Add dialect schema for hyperschema 2019-09 with schema 2020-12 #1133
Conversation
This file contains 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
jdesrosiers
force-pushed
the
202012-add-201909-hyperschema-dialect
branch
from
4ba71e4
to
8d342b2
Compare
jdesrosiers
force-pushed
the
202012-add-201909-hyperschema-dialect
branch
from
8d342b2
to
b9b0777
Compare
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.
Fixes #1120
Related to #1132
This is more complicated than it normally would be because 2019-09 and 2020-12 use different dynamic scope keywords and
$recrusiveRefdoesn't do everything it needs to do. In the future, we would only need to write the dialect schema and can reuse the vocabulary and links schemas.