mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-12 03:48:56 +00:00
6cc81584b9
JSON Schema allows "type" to be an array (e.g. ["string", "null"]) for a nullable/optional field, the shape Pydantic's model_json_schema() emits for Optional[str] / str | None. A real Azure DevOps MCP tool schema (testplan_test_suite_write) declares its optional parameters exactly this way. Both ToolTestPanel (the MCP Tool Testing Playground) and MCPToolArgumentsForm (the chat playground's tool-call argument form) compare a property's type with strict equality against a single string, with no fallback for the array case. In ToolTestPanel this leaves the field with no input at all, since none of the type checks match and there is no default branch: the field's label renders with nothing to type into, and the same strict comparison in the submit-time value conversion would also skip type coercion for it. MCPToolArgumentsForm has a final else branch, so the same schema shape instead renders the wrong widget (a plain text input for what should be a number or boolean field). Add resolveSchemaType to both files, resolving to the first non-"null" type when given an array, and use it everywhere a property's type decides a widget or a value conversion. Widen InputSchemaProperty.type in the shared types module to string | string[] to match. |
||
|---|---|---|
| .. | ||
| 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.