-
-
Notifications
You must be signed in to change notification settings - Fork 806
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
feat: filter by operation ids #929
feat: filter by operation ids #929
Conversation
3198861
to
e678279
Compare
I would also appreciate a look here @deepmap-marcinr and sorry about the spam :-( This is the last one, promise :-) |
e678279
to
7a85238
Compare
@deepmap-marcinr is this something, which would be acceptable for this repository? Happy to further elaborate on our use-case. |
Hey @johanneswuerbach thanks for raising! Would you mind adding an example of the usage under Once done, I'd say we can merge 😁 |
34efa3a
to
255ac80
Compare
Thanks for the review @jamietanna , integration tests added 👍 |
@jamietanna anything else I can support here? Thank you 🙇 |
255ac80
to
6f01e97
Compare
6f01e97
to
0b43f56
Compare
@jamietanna I know you are busy, but I wondered if there is any chance to land this :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this!
When generating server mocks or clients we often only need specific operations to be included. Right now we workaround this issue by having unique operation tags, but this has various side-effects.
Add the capability to include or exclude specific operations by their operation id inline with the existing support to filter by tags.