mirror of
https://github.com/BerriAI/litellm.git
synced 2026-11-07 07:58:09 +00:00
6fe0263761
* fix(ui): prefill the key edit Organization picker from org_id The Virtual Keys table hands KeyEditView rows from /key/list, which serializes the organization as org_id, while /key/info calls the same field organization_id. The edit form read only organization_id, so on a key opened from the list the Organization picker fell back to its "All Organizations" placeholder even though the key belongs to an org. Read both field names through one keyOrganizationId helper, used by the form value mapper, the edit view's selected organization state, and the two places in key_info_view that already hand-rolled the same fallback. * fix(ui): keep the key edit team filter in sync with the organization field * fix(ui): drop the leftover organization setter calls in the key edit team handler The previous commit derived the organization from the form and removed the useState behind it, but handleTeamChange still called the deleted setter, so the dashboard build failed to type check and picking a team with an organization threw at runtime. The form.setValue calls next to them already carry the organization, so the setter calls only had to go. Adds a test that picks a team with an organization and asserts the form adopts and submits it. * fix(ui): drop the list row's stale org_id when a key save returns its organization * fix(ui): send the key's organization only when the edit form changes it An untouched save from the key edit form now leaves organization_id out of the /key/update body, the same way the form already drops unchanged gated fields. This stops a save from writing a team's fallback organization onto a key that has none, and keeps the audit log free of no-op organization updates. The organization tests now use typed inputs * fix(ui): open team page keys with their own organization in the edit form * fix(ui): keep every team in the key form's team list for users who cannot change the organization --------- Co-authored-by: mateo-berri <edgetonmas@gmail.com> |
||
|---|---|---|
| .. | ||
| .agents/skills/url-state | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| vendor | ||
| .env.development | ||
| .env.production | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| AGENTS.md | ||
| build_release_ui.sh | ||
| build_ui.sh | ||
| build_ui_custom_path.sh | ||
| components.json | ||
| eslint-budgets.json | ||
| eslint-suppressions.json | ||
| eslint.config.mjs | ||
| knip.json | ||
| next.config.mjs | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.production.json | ||
| vitest.config.ts | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.