-
Notifications
You must be signed in to change notification settings - Fork 476
Allow Security Definitions Objects to be defined #471
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
Conversation
Can you add some specs for this feature? Thanks. |
@Bugagazavr Yep; I didn't purely because the existing |
@@ -278,6 +278,8 @@ add_swagger_documentation \ | |||
This value is added to the `authorizations` key in the JSON documentation. | |||
|
|||
|
|||
#### *security_definitions*: | |||
This value is added to the `securityDefinitions` key in the JSON documentation. | |||
|
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.
maybe adding the spec #security-definitions-object link,
so that the people have an idea
@bendodd … thanks, please add specs to have some usage examples and update the changelog, |
@LeFnord Added. Let me know what you think? |
@bendodd … loos ok to me :) … please run |
Damn it @LeFnord - that is school boy! Apologies; Fixed... |
👍 … thanks 😄 |
* Add securityDefinitions to allow Swagger UI to authenticate * Add usage docs and tests for security_definitions * Fix Rubocop errors #badben
Add securityDefinitions to allow Swagger UI to authenticate
A basic solution for #432