Add instructions on how to obtain Brand Logo Client ID API

[ampersandru]

Due to some confusion and complexity of multiple Brand API and what Client ID to use, adding instructions to the self-hosting settings page

Summary by CodeRabbit

• New Features
  • Added an inline, ordered walkthrough in Brand Fetch settings (displayed when the Client ID isn't configured) that guides users to create a developer account, open the Logo API page, reveal the Client ID, and paste it into the settings.

[coderabbitai]

Walkthrough

Adds an instructional HTML block to the Brand Fetch settings template that displays three ordered steps with external links when the BRAND_FETCH_CLIENT_ID environment variable is not configured.

Changes

Cohort / File(s)	Summary
UI Enhancement app/views/settings/hostings/_brand_fetch_settings.html.erb	Inserted an instructional <div> containing an ordered list with three steps and external links guiding users to create a Brandfetch developer account, open the Logo API page, and reveal/paste the Client ID when BRAND_FETCH_CLIENT_ID is unset.

Sequence Diagram(s)

Not applicable — UI-only change with no control-flow or new interactions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A helpful paw extends with grace,
Three links now guide you to your place,
When secrets hide and IDs sleep,
Instructions beckon, clear and deep.
Hop on, paste, and finish the leap! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Add instructions on how to obtain Brand Logo Client ID API" directly and clearly summarizes the main change in the changeset. The title is concise, specific, and uses descriptive language that accurately reflects what was added—instructional content for users to understand how to obtain the Brand Logo Client ID. A teammate scanning the repository history would immediately understand that this PR adds guidance for obtaining the Client ID, which is exactly what the changes accomplish. The title avoids vague terms and provides sufficient clarity about the primary intent of the changeset.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bf6a146 and 5cd9bfe.

📒 Files selected for processing (1)

• app/views/settings/hostings/_brand_fetch_settings.html.erb (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• app/views/settings/hostings/_brand_fetch_settings.html.erb

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 03cac95 and 601f99c.

📒 Files selected for processing (1)

• app/views/settings/hostings/_brand_fetch_settings.html.erb (1 hunks)

🧰 Additional context used

📓 Path-based instructions (15)

app/views/**/*.erb

📄 CodeRabbit inference engine (AGENTS.md)

app/views/**/*.erb: Keep heavy logic out of ERB views; prefer helpers/components instead
ERB templates are linted by erb-lint per .erb_lint.yml

Always use the icon helper (icon) for icons; never call lucide_icon directly

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

app/views/**/*.html.*

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

app/views/**/*.html.*: Use partials only for simple, context-specific, mostly static HTML content.
Prefer semantic HTML; use Turbo Frames where possible instead of client-side solutions.
Use query params for state, not localStorage or sessionStorage.
Always perform server-side formatting for currencies, numbers, and dates.

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

**/*.{html,erb,slim,js,jsx,ts,tsx,css,scss}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Always use functional design tokens (e.g., text-primary, bg-container) from the design system; do not use raw colors or ad-hoc classes.

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

**/app/**/*.erb

📄 CodeRabbit inference engine (CLAUDE.md)

Always use the icon helper for icons in templates; never use lucide_icon directly.

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

**/app/views/**/*.erb

📄 CodeRabbit inference engine (CLAUDE.md)

**/app/views/**/*.erb: Keep domain logic OUT of view templates; logic belongs in component files, not templates.
Use partials only for primarily static, simple HTML with minimal logic, and only when not likely to be reused.
Prefer native HTML over JavaScript components for UI elements (e.g., use <dialog>, <details><summary>).
Leverage Turbo frames for page sections over client-side JavaScript solutions.
Use query params (not localStorage/sessions) for client state management.
Perform server-side formatting for currencies, numbers, and dates in templates.

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

**/app/**/*.{rb,erb,js,css}

📄 CodeRabbit inference engine (CLAUDE.md)

Push Rails to its limits before adding new dependencies; a strong technical/business reason is required for new dependencies.

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

**/*.{rb,erb,haml,slim}

📄 CodeRabbit inference engine (.cursor/rules/general-rules.mdc)

**/*.{rb,erb,haml,slim}: Use Current.user for the current user; do not use current_user
Use Current.family for the current family; do not use current_family
Ignore i18n methods; hardcode strings in English for now (do not use I18n.t, t, or similar)

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

app/views/**/*.html.erb

📄 CodeRabbit inference engine (.cursor/rules/project-conventions.mdc)

app/views/**/*.html.erb: Prefer native HTML elements (e.g., ,

) over JS-based components
Leverage Turbo frames to break up pages instead of JS-driven client-side solutions
Prefer native client-side form validation when possible

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

app/{models,controllers,views}/**/*.{rb,erb}

📄 CodeRabbit inference engine (.cursor/rules/project-conventions.mdc)

Avoid N+1 queries

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

{app/javascript/controllers/**/*.{js,ts},app/views/**/*.erb,app/components/**/*.erb}

📄 CodeRabbit inference engine (.cursor/rules/stimulus_conventions.mdc)

Use declarative Stimulus actions in ERB (data-action) instead of imperative event listeners in controller lifecycle (e.g., avoid addEventListener in connect); controllers should just respond to actions

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

{app/components/**/*.{js,ts,erb},app/views/**/*.erb}

📄 CodeRabbit inference engine (.cursor/rules/stimulus_conventions.mdc)

Component-scoped Stimulus controllers in app/components must be used only within their component views, not in app/views

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

{app/views/**,app/helpers/**,app/javascript/controllers/**}

📄 CodeRabbit inference engine (.cursor/rules/ui-ux-design-guidelines.mdc)

{app/views/**,app/helpers/**,app/javascript/controllers/**}: Style UI using TailwindCSS v4.x with the custom design system defined in app/assets/tailwind/maybe-design-system.css
Always start by referencing app/assets/tailwind/maybe-design-system.css to understand available primitives, functional tokens, and component tokens before styling
Prefer functional tokens from the design system over raw Tailwind values (e.g., use text-primary, bg-container, border border-primary instead of text-white, bg-white, border-gray-200)

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

{app/views/**,app/helpers/**}

📄 CodeRabbit inference engine (.cursor/rules/ui-ux-design-guidelines.mdc)

Always generate semantic HTML

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

{app/views,app/components}/**/*.html.erb

📄 CodeRabbit inference engine (.cursor/rules/view_conventions.mdc)

{app/views,app/components}/**/*.html.erb: Keep domain logic out of ERB templates; compute values in component/controller code and reference them in the template
Integrate Stimulus declaratively in ERB: templates declare data-controller/data-action; controllers respond to those declarations
Pass data from Rails to Stimulus via data-*-value attributes, not inline JavaScript

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

app/views/**/_*.html.erb

📄 CodeRabbit inference engine (.cursor/rules/view_conventions.mdc)

Name partials with a leading underscore (e.g., _trend_change.html.erb, _form_errors.html.erb)

Files:

• app/views/settings/hostings/_brand_fetch_settings.html.erb

[ampersandru]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[jjmata]

LGTM!