We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This would allow us to only generate a subset of the interfaces/methods we need.
e.g. App might need "Configuration"-Controller/Group Methods, but not others.
by allowing things like the following, the consumers can specify exactly what they need. matches are based on regex
--include '^/api/v1/user/.*' --include '^/api/(?!pet\b)' // include everything that is NOT /api/pet
For a less fine grained, but also useful way, we could also add filter for the "Tags" section of an openapi spec.
matches are based value, case-insensitive
--include-tag User \ --include-tag Configuration
The text was updated successfully, but these errors were encountered:
@kirides That's a really good idea!
Sorry, something went wrong.
christianhelle
Successfully merging a pull request may close this issue.
This would allow us to only generate a subset of the interfaces/methods we need.
e.g. App might need "Configuration"-Controller/Group Methods, but not others.
by allowing things like the following, the consumers can specify exactly what they need.
matches are based on regex
For a less fine grained, but also useful way, we could also add filter for the "Tags" section of an openapi spec.
matches are based value, case-insensitive
The text was updated successfully, but these errors were encountered: