Fix old draft-07 schema in 2020 schema#13
Open
tarjelavik wants to merge 2 commits into
Open
Conversation
Author
|
Removed in latest commit |
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.
Fix #12, #8
AI helped fix and write this issue... :-/
The problem: schema/core.json declares $schema: draft 2020-12, but the ContextStringOrArray definition used the draft-07 tuple form of items (an array of subschemas):
In draft 2020-12, items must be a single schema (object or boolean) and applies to all array elements; the tuple/positional form was renamed to prefixItems. That's why the metaschema rejected /definitions/ContextStringOrArray/anyOf/1/items with "want boolean or object, but got array."
Since the intent is "an array of context URI strings," I changed it to apply the subschema to every item: