Allow the user to provide a list of specific kube markers to be ignored #27
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
|
Issues linked to changelog: |
shashankram
reviewed
Aug 7, 2024
shashankram
reviewed
Aug 7, 2024
shashankram
reviewed
Aug 7, 2024
jjamroga
commented
Aug 7, 2024
jjamroga
commented
Aug 7, 2024
shashankram
approved these changes
Aug 7, 2024
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.
Use Case
I'm defining a proto that relies on some upstream dependency that also contains their own kube markers. These kube markers exist only for documentation, and do not affect the open api schema. Rather than implement noop markers to add to a marker registry, I would like to simply ignore them.