draft-next "contains", "minContains", "maxContains", and related "unevaluatedProperties" support #95
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.
Fixes #93. I was cleaning up local branches and realized I never posted this one. I don't expect this to go into 0.10.1 but (like the PRs I rebased today) I had to put the CHANGELOG entry somewhere. I expect to rebase and move it whenever appropriate.
"contains" now supports both objects and arrays, and while it produces the same annotations, it now reads annotations from
minContains and maxContains, which no are no longer assertions.
"contains" now also impacts "unevaluatedProperties", so that keyword gets a new version as well.
This also removes the need to ever un-fail another keyword's result, although the pass_() method still has other internal uses.