[UI] Rename "Default" key type to "Full Access" and reorder dropdown - #27218
Merged
ryan-crabbe-berri merged 1 commit intoMay 9, 2026
Merged
Conversation
The Create New Key dialog had a "Default" key-type option that was
misleading: it was not the actual default selection (AI APIs is), and it
grants access to all routes — broader than the description implied.
Rename the option to "Full Access" with an accurate description, and
reorder the dropdown to AI APIs → Management → Full Access. Switch the
inner labels to antd Typography for consistency with the rest of the UI.
UI-only change; the underlying enum value ("default") is unchanged so
the API contract is preserved.
Contributor
Greptile SummaryThis is a purely cosmetic UI change to the Create New Key dialog that renames the misleading "Default" key-type option to "Full Access" and moves it to the end of the dropdown so the preselected "AI APIs" option appears first.
Confidence Score: 5/5Safe to merge — purely cosmetic, no logic or API contract changes. The change only touches dropdown label text, option ordering, and a swap from raw div markup to antd Typography components. The "default" enum value, form initialValue, and defaultValue are all left untouched, so no backend or stored-state impact is possible. No files require special attention.
|
| Filename | Overview |
|---|---|
| ui/litellm-dashboard/src/components/organisms/create_key_button.tsx | Renames the "Default" key-type option to "Full Access", reorders the dropdown (AI APIs → Management → Full Access), and replaces raw div-based label markup with antd Typography.Text/Typography.Paragraph. The underlying "default" enum value and form initialValue/defaultValue are preserved. |
Reviews (1): Last reviewed commit: "[UI] Rename "Default" key type to "Full ..." | Re-trigger Greptile
yuneng-berri
approved these changes
May 5, 2026
ryan-crabbe-berri
merged commit May 9, 2026
0f11b3e
into
litellm_internal_staging
113 of 115 checks passed
2 tasks
Setsuna-Yukirin
pushed a commit
to Setsuna-Yukirin/litellm
that referenced
this pull request
May 9, 2026
The antd mock omits Typography, which caused all 15 tests in create_key_button.test.tsx to fail with "No 'Typography' export is defined on the 'antd' mock" after BerriAI#27218 switched the key-type dropdown labels to Typography.Text / Typography.Paragraph. Add Typography (with .Text, .Paragraph, .Title subcomponents) to the mock so the dropdown renders in the test environment.
fzowl
pushed a commit
to fzowl/litellm
that referenced
this pull request
Jun 24, 2026
…erriAI#27218) The Create New Key dialog had a "Default" key-type option that was misleading: it was not the actual default selection (AI APIs is), and it grants access to all routes — broader than the description implied. Rename the option to "Full Access" with an accurate description, and reorder the dropdown to AI APIs → Management → Full Access. Switch the inner labels to antd Typography for consistency with the rest of the UI. UI-only change; the underlying enum value ("default") is unchanged so the API contract is preserved.
fzowl
pushed a commit
to fzowl/litellm
that referenced
this pull request
Jun 24, 2026
The antd mock omits Typography, which caused all 15 tests in create_key_button.test.tsx to fail with "No 'Typography' export is defined on the 'antd' mock" after BerriAI#27218 switched the key-type dropdown labels to Typography.Text / Typography.Paragraph. Add Typography (with .Text, .Paragraph, .Title subcomponents) to the mock so the dropdown renders in the test environment.
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.
Resolves LIT-2680.
Summary
The Create New Key dialog (Virtual Keys page) had a "Default" key-type option that was misleading on two counts:
This PR:
<div>-based label/description markup withantdTypography.Text/Typography.Paragraphfor consistency with the rest of the UI.UI-only change. The underlying enum value (
"default") is unchanged, so the/key/generateAPI contract and existing keys are unaffected.Screenshot
Test plan