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

Introduce filter capability #6

Closed
arthurdm opened this issue Oct 18, 2017 · 1 comment
Closed

Introduce filter capability #6

arthurdm opened this issue Oct 18, 2017 · 1 comment
Assignees
Labels

Comments

@arthurdm
Copy link
Member

arthurdm commented Oct 18, 2017

We need to introduce a Filter service/interface that would allow application developers to take control before/during/after the annotation processing stage.

This means that dev have the flexibility to programmatically start an OAS tree that the processor uses, or filter certain operations/objects dynamically. Devs could even do a "model-only" approach, which would turn off annotation processing.

Proposed name: OASFilter

This was referenced Oct 18, 2017
janamanoharan pushed a commit to janamanoharan/microprofile-open-api that referenced this issue Oct 19, 2017
Factoring out a base interface for extension related methods.
@arthurdm arthurdm added the design label Nov 9, 2017
@arthurdm arthurdm self-assigned this Nov 13, 2017
@arthurdm
Copy link
Member Author

Delivered via #32

Azquelt pushed a commit to Azquelt/microprofile-open-api that referenced this issue Mar 17, 2022
* Additional "extra" TCK test for testing complex types.

Signed-off-by: Eric Wittmann <eric.wittmann@gmail.com>

* renamed the readme and added a license header

Signed-off-by: Eric Wittmann <eric.wittmann@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant