Skip to content
New issue

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

Proposal: filter generated interfaces #131

Closed
kirides opened this issue Aug 30, 2023 · 1 comment · Fixed by #132
Closed

Proposal: filter generated interfaces #131

kirides opened this issue Aug 30, 2023 · 1 comment · Fixed by #132
Assignees
Labels
bug Something isn't working

Comments

@kirides
Copy link
Contributor

kirides commented Aug 30, 2023

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
@christianhelle
Copy link
Owner

@kirides That's a really good idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants