Repository navigation
Keep a model's answer when it comes back in the shape of the schema - #2
Merged
Merged
Conversation
Small models shown a JSON Schema often nest correct values under "properties" next to $schema/type/required, so validation reported every field undefined. Unwrap that and a wrapper named after the object, and stop sending the meta keys that invite the copy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
qwen3.5 9B answered crawlproof ad copy as a copy of the JSON Schema with the right values under
properties, so validation failed with every field undefined.unwrapEchorecovers that and a wrapper named after the object;jsonInstructionsdrops the$schema/$idkeys and says not to echo. Bumps 0.1.1.🤖 Generated with Claude Code