Repository navigation
Conversation
|
|
1 similar comment
|
|
Signed-off-by: percymcn <securepharma11@gmail.com>
percymcn
force-pushed
the
add-llm-json-schema
branch
from
August 9, 2026 01:25
2acea65 to
8ad9504
Compare
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 LLM JSON Schema as a
toolentry.What it is: a free, client-side web tool that takes an arbitrary JSON Schema and rewrites it into the restricted dialect subset each LLM provider actually accepts for structured outputs — OpenAI, Anthropic, and Gemini. Every transform it applies is annotated with the specific provider documentation rule that requires it (e.g. OpenAI requiring
additionalProperties: falseand every property listed as required), and keywords a provider silently drops are flagged rather than quietly removed.Relationship to Schema Gateway (already listed): that entry solves the same problem from the CLI/CI/hosted-API direction. This one is the zero-install case — it runs entirely in the browser with no upload, which matters when the schema is from a private codebase. They complement rather than duplicate each other.
Per CONTRIBUTING.md: the entry was added to
data.yamland the README regenerated withnpm install && npm start; both files are included.npm startvalidated the entry againstschema.jsonsuccessfully. The unrelatedpackage-lock.jsonchurn fromnpm installwas reverted, so the diff is only those two files.