mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-14 23:21:35 +00:00
2a12707372
* refactor(ui): colocate the policies view, keeping PolicySelector shared Group-1 colocation split. The policies folder lived in the shared src/components dump but is only partly shared: PolicySelector (used by the Playground, ComplianceUI, and key edit view) and its types stay in @/components/policies, while the policy-management view (27 files: index, tables, forms, modals, pipeline builder, and their tests) moves to policies/_components. Moved files' imports of the retained shared files become @/components/policies paths; other escaping relative imports are absolutized against the @/ alias (including @/data/... and the repo test-utils via @/../tests/...), and moved test files have both their `from` imports and `vi.mock` paths rewritten so the mocks keep matching the source. Grandfathered lint suppressions for moved files are re-keyed. PolicySelector did not move, so its external consumers are untouched. No behavior change. * fix(ui): keep PolicySelector.tsx eslint suppression at its original path PolicySelector.tsx stays in src/components/policies (only the management view moved to _components), but the suppression re-key wrongly moved its no-nested-ternary entry to the phantom _components path, orphaning the real file's suppression. Revert that one key. (Greptile P1 on #32720.) |
||
|---|---|---|
| .. | ||
| e2e_tests | ||
| 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-metrics.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.