Polish JSON ingestion schema API extensions#1213
Merged
jwils merged 0 commit intoMay 27, 2026
Merged
Conversation
24dff3c to
a3bc7c1
Compare
88b1d9c to
3436470
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.
Why
Keep the JSON ingestion API polish separate from the README-only docs PR while preserving the stack order after JSON ingestion becomes a default schema-definition extension.
What
Risk Assessment
Medium — this changes internal schema-definition extension wiring while preserving the generated JSON schema behavior.
References
script/lint,script/type_check,script/spellcheck,git diff --check, and affected schema-definition specs passed.