-
-
Notifications
You must be signed in to change notification settings - Fork 328
re-unite meta-schema #1610
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
base: main
Are you sure you want to change the base?
re-unite meta-schema #1610
Conversation
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.
Looks good. Thanks for doing this work.
Left one comment, but not essential.
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.
Looks good to me
specs/meta/meta.json
Outdated
"$schema": "https://json-schema.org/version/year/meta", | ||
"$id": "https://json-schema.org/version/year/meta", |
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.
What's "meta"? (Sorry if it's something we discussed and I forgot.)
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.
Also, what's the reason for using a placeholder for "version" and "year"?
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.
What's "meta"?
it was late. It should just be /version/year
Also, what's the reason for using a placeholder for "version" and "year"?
It's not published yet. Just wanted to communicate the idea.
@jdesrosiers I've updated the $-keyword restriction using your suggestion. It's a bit direct, but simple is probably better anyway. |
What kind of change does this PR introduce?
Refactor
Issue & Discussion References
Summary
Re-unites the meta-schema into a single file since vocabularies are a proposal now. We will likely split it back up again when we figure out vocabs, but for now it doesn't make sense to have them separated.
Also:
x-*
keywords$*
keywordsDoes this PR introduce a breaking change?