feat(client): provider checklist UI on the Keys page (#543) - #596
Open
gaurang-py wants to merge 2 commits into
Open
feat(client): provider checklist UI on the Keys page (#543)#596gaurang-py wants to merge 2 commits into
gaurang-py wants to merge 2 commits into
Conversation
Adds a dashboard endpoint that enumerates every registered provider with whether at least one key has been added yet, so users can see what's still missing without scrolling the full list (tashfeenahmed#543). The existing /api/health endpoint only reports platforms that already have keys, so there was no way to list the not-yet-configured providers. Returns, per provider, { platform, name, keyless, configured, keyCount, enabledKeyCount } plus a { total, configured, unconfigured } summary, sorted by display name. Sourced from the runtime provider registry (getAllProviders) so it stays in sync as providers are added; the `custom` placeholder is excluded since it's a per-key user-defined entry, not a fixed provider to check off. Behind the existing dashboard-session auth like the rest of /api/keys. Adds route tests (auth required, all-unconfigured shape, configured after a key is added). Full server suite green.
Adds an at-a-glance checklist above the provider key manager showing every
built-in provider and whether a key has been added yet (✓/✗), with a
"{configured} of {total} providers set up" summary, so users can see what's
left to configure without scrolling the full list (tashfeenahmed#543).
Consumes the GET /api/keys/providers endpoint. Read-only, react-query like the
rest of the page; keyless providers (Kilo, OVH, AI Horde) are tagged "no key
needed". Hidden while loading / when empty. English strings added; other
locales fall back to English until translated.
Verified via tsc -b + vite build + eslint (the repo has no client-side test
harness). Backend contract is covered by the server-side test added with the
endpoint.
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
1 participant
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.
Adds the dashboard UI for #543, on top of the
/api/keys/providersendpoint from #595.What it does
A compact, read-only checklist at the top of the Providers tab on the Keys page: every built-in provider with a ✓ (key added) or ✗ (not yet), plus a
"{configured} of {total} providers set up"summary — so you can see what's left to configure without scrolling the key manager and enumerating by hand.GET /api/keys/providersvia react-query, exactly like the rest of the page (apiFetch, dashboard-session auth handled by the wrapper).providerstab (no new tab, minimal plumbing).i18n
Three English strings added under
keys.*(checklistTitle,checklistSummary,checklistKeyless). The custom i18n falls back to English for the other five locales, so everything renders; happy to add translations (or defer to the translation effort in #315) — let me know your preference.Testing / verification
The client has no test harness (no vitest/testing-library in
client/), so — consistent with the repo — this is verified via:npm run build -w client(tsc -b && vite build) — passeseslinton the changed files — clean (the repo's pre-existing lint errors are in unrelated files)I mirrored the existing
provider-list.tsxcard/row idiom and lucideCheck/Xusage to keep it visually consistent. I can't click-test it here, so I kept it deliberately minimal — flagging that honestly.Closes #543 together with #595.