This repository has been archived by the owner on Jan 27, 2022. It is now read-only.
Refactor approach to generating .schema.json
#46
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This implements #41. I'm merging it now but pinging @alex-ketch @apawlik and @beneboy so they see the documentation / changes below esp in
CONTRIBUTING.mdandGulpfile.jsbut also how the.schema.yamlfiles are now authored.New properties on
dist/*.schema.jsonfiles that may be of use in docs:category- what we where calling "groups"role- to help prioritize writing of docs and maybe level of emphasis in sidebar navstatus- to indicate experimental and unstable schemasI have not filled in
roleandstatusfor all schemas yet.