fix(provider-utils): ensure 'type: object' in JSON schemas for DeepSeek/OpenAI compatibility #12283
Conversation
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
Author
|
Hey @lgrammel, I took a look at #7924 regarding the missing I've implemented a fix in Let me know if you'd like me to iterate on any of this! |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Ashutosh0x
force-pushed
the
fix/deepseek-schema-type-object
branch
from
744b9ae to
3b37b03
Compare
## Title fix(provider-utils): ensure 'type: object' in JSON schemas for DeepSeek/OpenAI compatibility ## Body Fixes vercel#7924 ### Problem Some providers like DeepSeek and other OpenAI-compatible APIs fail when the tool/input schema is missing the explicit `type: 'object'` property, even if `properties` and `additionalProperties` are defined. ### Solution - Modified the `jsonSchema` getter in the `Schema` type to automatically add `type: 'object'` when `properties` are present but `type` is missing. - Updated the default schema returned by `asSchema(undefined)` to explicitly include `type: 'object'`. ### Impact Improves reliability for providers with stricter schema requirements (DeepSeek, etc.). ## Human-like Comment for @lgrammel Hey @lgrammel, I took a look at vercel#7924 regarding the missing `type: object` in schemas for DeepSeek and other providers. I've implemented a fix in `provider-utils` that ensures `type: 'object'` is automatically included whenever `properties` are defined. I also updated the default empty schema. Added a new test file `packages/provider-utils/src/schema-deepseek-fix.test.ts` to verify everything works as expected. Let me know if you'd like any changes!
Ashutosh0x
force-pushed
the
fix/deepseek-schema-type-object
branch
from
3b37b03 to
3a2324b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pull Request: fix(provider-utils): ensure 'type: object' in JSON schemas for DeepSeek/compatibility
Fixes #7924
Problem
Some providers like DeepSeek and other OpenAI-compatible APIs fail when the tool/input schema is missing the explicit
type: 'object'property, even ifpropertiesare defined.Changes
packages/provider-utils/src/schema.tsto automatically addtype: 'object'to JSON schemas whenpropertiesare present buttypeis missing.asSchema(undefined)to includetype: 'object'in its default schema.packages/provider-utils/src/schema-deepseek-fix.test.tsto verify the fix..eslintignoreto prevent ESLint from parsing largedistdirectories in any package (fixes "missing semicolon" errors in.mapfiles).rm -rfwithdel-cli(already a dependency) in several packages to ensurepnpm cleanandpnpm buildwork correctly on Windows.package.jsonfiles to targetsrc/explicitly, avoiding build artifacts.Verification
pnpm buildandpnpm lintnow pass on Windows locally.