feat(swagger): add extension in SecuritySchemeObject#3247
Closed
mag123c wants to merge 7 commits intonestjs:masterfrom
Closed
feat(swagger): add extension in SecuritySchemeObject#3247mag123c wants to merge 7 commits intonestjs:masterfrom
mag123c wants to merge 7 commits intonestjs:masterfrom
Conversation
Feature/3157 add document enabled option
Contributor
Author
|
I think we just need to add extension to SecuritySchemeObject like this commit. Additionally, I don't see the test code either. Is there anything else we need to consider for adding extension? |
Contributor
Author
|
This PR contains unnecessary commits due to a branch synchronization issue. I will close this PR and open a new one with only the relevant changes!! |
This file contains hidden or 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
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
SecuritySchemes cannot include additional necessary information. Specifically, for security implementations requiring more than one header, the current
Security Scheme Objectcannot represent such configurations. This limitation makes it difficult to express security setups for platforms like AWS API Gateway, which often require additional metadata.Issue Number: #3179
What is the new behavior?
Added support for custom extension properties in the
SecuritySchemeObjectexample code when used
addApiKey()When creating a Swagger document, you can now include custom extensions in the Security Scheme Object using methods like .addApiKey(), .addBearerAuth(), .addOAuth2(), or .addBasicAuth(). This feature enables you to define additional metadata required for platforms like AWS API Gateway or other custom security configurations.
Does this PR introduce a breaking change?
Other information
reference: https://swagger.io/docs/specification/v3_0/openapi-extensions/