MOSIP-45483(nexus-ui): add step-by-step API key generation guide to Settings page - #95
Merged
Merged
Conversation
New users landing on Settings had only a bare link ("Get a free key at
console.groq.com") and no sense of what to actually do once they got
there. Add a collapsible "How do I get a {Provider} API key?" walkthrough
above the key field, matching the existing <details>/<summary> pattern
already used for the MCP setup guide on the same page.
PROVIDER_META gains keySteps (numbered instructions) and an optional
keyNote (free-tier vs billing-required) per provider, covering all four
supported providers: Groq, Anthropic, OpenAI, xAI. The guide swaps
automatically when the user switches provider chips, since it reads off
the same PROVIDER_META[llmProvider] already driving the key hint/link.
Signed-off-by: Mohanachandran S <mohanachandran.s@technoforte.co.in>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 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. Comment |
jayesh12234
approved these changes
Aug 20, 2026
lsivanand
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Settings page's API key field only had a bare link ("Get a free key at
console.groq.com") with no indication of what to actually do once there —
first-time users had to figure out the whole signup/key-creation flow on
their own, per provider.
Fix
Add a collapsible "How do I get a {Provider} API key?" walkthrough right
above the key input, using the same
<details>/<summary>patternalready used for the MCP setup guide further down the same page.
PROVIDER_METAgains:keySteps: string[]— numbered instructions (sign in → find API keys →create → copy → paste), tailored per provider's actual console UI
keyNote?: string— a one-line caveat where relevant (e.g. Anthropic/OpenAI require billing set up; Groq has a free tier)
Covers all four supported providers: Groq, Anthropic, OpenAI, xAI. The
guide swaps automatically when switching provider chips, since it reads
off the same
PROVIDER_META[llmProvider]already driving the existingkey hint/link.
Testing
npx tsc -p tsconfig.app.json --noEmit— passes🤖 Generated with Claude Code