-
Notifications
You must be signed in to change notification settings - Fork 474
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(api-extension): add support for open api extensions via decorator (#195) #536
feat(api-extension): add support for open api extensions via decorator (#195) #536
Conversation
This commit adds support for Open API Extensions via a @APIextension decorator. Usage: ``` @APIextension(<extensionName>, <extensionPropertyObject>) ``` Example: ``` @APIextension('x-foo', { hello: 'world' }) ```
@kamilmysliwiec Do you know when you can make this PR available? |
@tomchinery thank you! Would you like to create a PR to the docs as well? |
Sure, will do so now! |
Amazing, thank you @tomchinery! |
@kamilmysliwiec The docs PR is pushed up here: nestjs/docs.nestjs.com#1021. Let me know if there's anything else needed. Thanks! |
Thank you! |
@tomchinery @kamilmysliwiec Thanks for adding this support for api extensions to swagger docs. How can I add multiple ApiExtensions? My company's swagger validation requires that I add 4 different
|
@elizabetht Please create a separate issue and share a minimum reproduction repository 🙌 |
This commit adds support for Open API Extensions via a @APIextension decorator.
Usage:
Example:
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?
Issue Number: Solves #195
What is the new behavior?
Adds an extension to the Swagger Specification:
Does this PR introduce a breaking change?
Other information