Repository navigation
Add schema-envoy to tools - #58
Merged
Merged
Conversation
Contributor
Author
Signed |
Member
|
Awesome! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
schema-envoyunder tools.Every LLM provider accepts a subset of JSON Schema, so client libraries delete the keywords the provider does not list. That deletion widens the accepted value set (the converted schema accepts instances the source schema rejects), and it is normally not reported.
schema-envoyperforms the conversion, reports every keyword it removed, and compiles a residual validator over precisely those dropped constraints, so a caller can reject a widened value rather than only learn that widening occurred.It is distinct from Schema Gateway, already listed: that entry compiles a schema into provider-ready request payloads and lints portability.
schema-envoy's output is the report and the residual validator over what conversion cost, rather than the request payload.Zero-config for the built-in provider targets, dual ESM/CJS, published with npm provenance.
I have added the entry to
data.yamland regeneratedREADME.mdwithnpm install && npm start, as CONTRIBUTING.md asks.