Repository navigation
Migration from OpenAPI 3.0 Schema Object to JSONSchema in Eino #397
mrh997
announced in
Announcements
Replies: 5 comments 3 replies
|
Great! Looking forward to this. Loving eino so far. |
0 replies
|
When I use but Is it possible to support dynamic modification of jsonschema.Schema? like |
2 replies
|
Do we have ETA for these features? |
1 reply
|
If migrating to JSON Schema is too complex, consider using these two alternative methods. OpenAPIV3ToJSONSchemaJSONSchemaToOpenAPIV3 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
📌 Summary
In the future, Eino will use JSONSchema Draft 2020-12 to replace OpenAPI 3.0 Schema Object to describe tool parameters. We will release v0.6.0 in November, at which time all OpenAPI 3.0 related codes will be removed.
❗Issues
Eino currently depends on kin-openapi@v0.118.0, which has a critical security vulnerability.
Most model platform protocols — such as OpenAI, ARK and Claude — specify that tool parameters should be described using JSONSchema. Likewise, the MCP protocol also suggests JSONSchema for tool parameters.
💡 Solution
✅ New Features
The two new methods planned are as follows:
⛔ Deprecated (will be removed in future releases)
All reactions