-
-
Notifications
You must be signed in to change notification settings - Fork 219
more test cases for unevaluatedItems, unevaluatedProperties #472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This prevents annotations collected so far from being improperly used by unevaluatedItems, unevaluatedProperties when only annotations from sibling keywords (or children of sibling keywords) should be used. See https://stackoverflow.com/questions/66936884/deeply-nested-unevaluatedproperties-and-their-expectations and json-schema-org/JSON-Schema-Test-Suite#472
This prevents annotations collected so far from being improperly used by unevaluatedItems, unevaluatedProperties when only annotations from sibling keywords (or children of sibling keywords) should be used. See https://stackoverflow.com/questions/66936884/deeply-nested-unevaluatedproperties-and-their-expectations and json-schema-org/JSON-Schema-Test-Suite#472
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think all of these test are necessary. It looks to me like we really only need the one test for each keyword. I might be missing something.
] | ||
}, | ||
{ | ||
"description": "item is evaluated in an uncle schema to unevaluatedItems", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "item is evaluated in an uncle schema to unevaluatedItems", | |
"description": "item is evaluated in a separate keyword branch to unevaluatedItems", |
"valid": true | ||
}, | ||
{ | ||
"description": "uncle keyword evaluation is not significant", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "uncle keyword evaluation is not significant", | |
"description": "evaluation of items in a separate keyword branch is not significant", |
] | ||
}, | ||
{ | ||
"description": "in-place applicator siblings, allOf has unevaluated", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "in-place applicator siblings, allOf has unevaluated", | |
"description": "property is evaluated in a separate keyword branch to unevaluatedProperties", |
cd99094
to
78feea2
Compare
I have removed the redundant tests (two in each file). I've left the test descriptions alone, as "uncle" is used to indicate the distinction from the other "sibling" and "cousin" tests. |
Only annotations from sibling keywords (or children of sibling keywords) should be used by unevaluatedItems, unevaluatedProperties, rather than all annotations collected so far. see https://stackoverflow.com/questions/66936884/deeply-nested-unevaluatedproperties-and-their-expectations
78feea2
to
ed4cf5f
Compare
This all seems to be sorted now, so I'm merging. |
This prevents annotations collected so far from being improperly used by unevaluatedItems, unevaluatedProperties when only annotations from sibling keywords (or children of sibling keywords) should be used. See https://stackoverflow.com/questions/66936884/deeply-nested-unevaluatedproperties-and-their-expectations and json-schema-org/JSON-Schema-Test-Suite#472
Thanks for handling this one! |
Only annotations from sibling keywords (or children of sibling keywords)
should be used by unevaluatedItems, unevaluatedProperties, rather than all
annotations collected so far.
see https://stackoverflow.com/questions/66936884/deeply-nested-unevaluatedproperties-and-their-expectations