Migration from OpenAPI 3.0 Schema Object to JSONSchema in Eino #397
Replies: 5 comments 3 replies
-
|
Great! Looking forward to this. Loving eino so far. |
Beta Was this translation helpful? Give feedback.
-
|
When I use but Is it possible to support dynamic modification of jsonschema.Schema? like |
Beta Was this translation helpful? Give feedback.
-
|
Do we have ETA for these features? |
Beta Was this translation helpful? Give feedback.
-
|
We have released v0.6.1. |
Beta Was this translation helpful? Give feedback.
-
|
If migrating to JSON Schema is too complex, consider using these two alternative methods. OpenAPIV3ToJSONSchemaJSONSchemaToOpenAPIV3 |
Beta Was this translation helpful? Give feedback.
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 [email protected], 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)
Beta Was this translation helpful? Give feedback.
All reactions