Handle object-shaped not schemas without crashing#1803
Open
morgan-coded wants to merge 1 commit into
Open
Conversation
|
Member
|
@morgan-coded hello hello!!!! |
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.
A
not: {}schema could reach the complex schema parser and crash because the parser expected complex keyword values to be arrays.This adds array guards for complex keyword parsing, so non-array values take the same empty-result path as before while array-valued
oneOf,anyOf, andallOfbehavior stays unchanged. I checked the issue repro against the failing path, then ran install, format, build, and the full test suite with 275 tests passing.Fixes #1798