Add rule to detect operation tags that are not defined in global tags object #704
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
|
This is great @mkistler! The docs mention is just a reminder to get people to see if anything in Tests are failing for some reason, but if you get them passing and docs added I'll hit merge on this thing! |
philsturgeon
approved these changes
Oct 24, 2019
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 adds a new operation validation that reports operation tag values that are not defined in the global tags array.
This new rule is marked as "recommended" and by default produces a warning message.
Note: "CONTRIBUTING.md" does not say anything about doc updates, so I'm not quite sure what I need to do there.
Does this PR introduce a breaking change?