Add "deprecated" field to the OpenAPIOperation struct #4
Conversation
This file contains hidden or 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.
I need to filter out some operations based on the
deprecatedfield. While it can be achieved by adding a new tag, we are already using thisdeprecated: truefield in our API specs.This PR is just to expose this field so that we can use it from other places.
I also wonder if we even want to embed the
*openapi3.Operationin theOpenAPIOperationstruct, but, for now, I kept the changes to a minimum.Also, we could have something similar to the
TagFilterand have this implemented here as well. Happy to do so, but before jumping in, I'd like to confirm/double-check it.PS: thank you for forking the original project and starting to maintain it!