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.
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.
Would have been better as
<4
?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.
How are you testing (how did you find out it was breaking?)
EDIT: I think I found it... I was in a branch and didn't realize it.
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.
This seems to be two things: in jsonschema==4.0.1 they added two new validators (latest is default, which ends up being jsonschema.validators.Draft202012Validator). Our schema doesn't seem to be valid in that latest hyperschema.
Also, the Draft201909Validator in the package seems to be broken.
For the moment the most appropriate fix is probably to add
"$schema": "http://json-schema.org/draft-07/schema#" to the top of our schema. This will allow it to work with jsonschema==4.0.1 and we should be versioning the hyperschema anyway.
I will put in a PR shortly - have to go to a meeting right now.
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.
python-jsonschema/jsonschema#847
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.
In the newest draft 2020-12 "items" functionality is largely replaced by "prefixItems", and "additionalItems" is replaced by "items" ("additionalItems" goes away). That is why our schema doesn't load in the latest validator.