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.

Sign up for GitHub

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

Jump to bottom

authorize sub-commands should be named for key in securityDefinitions object, not name property #19

Closed
gdereese opened this issue Feb 22, 2018 · 0 comments
Closed

authorize sub-commands should be named for key in securityDefinitions object, not name property #19

gdereese opened this issue Feb 22, 2018 · 0 comments
Labels
bug Something isn't working
Milestone
0.2.0

Comments

@gdereese
Copy link
Owner

No description provided.

@gdereese gdereese added the bug Something isn't working label Feb 22, 2018
@gdereese gdereese added this to the 0.2.0 milestone Feb 22, 2018
@gdereese gdereese changed the title authorize sub-commands should be named for key in securityDefinitions object, not name property authorize sub-commands should be named for key in securityDefinitions object, not name property Feb 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
0.2.0
Development

No branches or pull requests
1 participant
@gdereese