Registry sub-commands #30
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 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.
This PR sets up the registry command and defines a list of sub-commands (i.e., check, generate, resolve, search, stats). Only the
checkcommand is implemented (see #26).All other existing commands have been placed behind the
experimentalfeature flag so as not to appear by default.A brief description of the semantic convention registry resolution process has been added to the
README.mdof theweaver_resolvercrate. Unimplemented elements are also identified (i.e.,any_of,include). The completion and full testing of the registry resolution process will be the subject of a future PR.