Move SecurityScheme annotation to model mapping to core #4560
Conversation
This file contains 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
This moves the SecurityParser class responsible for populating SecurityScheme models from SecurityScheme annotations to the core module. The move allows using it without taking the dependency on JAX-RS.
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.
This moves the
SecurityParserclass responsible for populatingSecuritySchememodels fromSecuritySchemeannotations to thecoremodule.The move allows using it without taking a dependency on JAX-RS and to use it for building integrations for other technologies.
I'm opening this very simple pull request as a probe. Is moving the code for mapping annotations to models out of the jaxrs module desirable for the project? Some related code is already in the
AnnotationsUtilsclass in thecoremodule.