mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-05 02:41:56 +00:00
770a4feb8d
`handleSave` was 280 lines that parsed stdio JSON, filtered credentials, resolved half a dozen conditional flags, built the request body, and then made the network call, all inside one try block reading ten closure variables. None of it could be tested without rendering the whole modal and pressing Save. The payload building moves to `editServerPayload.ts` as `buildEditServerPayload`, mirroring the `createServerPayload.ts` module that already sits beside it: a pure function taking form values, UI state, and the server being edited, and returning a tagged union rather than throwing. The six ways it can fail are now values in that union, and the component maps them to the same toasts it showed before via an exhaustive switch, so no message text changes. `AUTH_TYPES_REQUIRING_CREDENTIALS` and the static-header reducer were duplicated between the create and edit paths; the extracted module imports the create module's copies instead. The credential filter and stdio parser stay separate, because the edit versions genuinely differ: edit writes an explicit null to clear a blanked admin-config key, and stringifies stdio args and env values where create passes them through Behaviour is unchanged, and the payload net added earlier is what proves it: all 20 of its cases still pass against the extracted builder without any edit to their expectations. 40 unit tests cover the new module in single-digit milliseconds, reaching the rejection paths and parsing branches that were previously only reachable through a full render. A ten-mutant battery kills 10/10, each mutant taking down exactly one test, which is the profile worth having: the tests are targeted rather than broadly overlapping One of those mutants is worth noting. Removing the access-group name normalisation survives the integration net but dies here, because the antd Select hands the form plain strings and the unit test does not. That mapping is dead only while that control stays; it is covered now either way |
||
|---|---|---|
| .. | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| .env.development | ||
| .env.production | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| build_release_ui.sh | ||
| build_ui.sh | ||
| build_ui_custom_path.sh | ||
| CLAUDE.md | ||
| 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.tsbuildinfo | ||
| 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.