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.

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

Security definition includes a description in the spec, is it not parsed? #480

Open
alkemann opened this issue Jul 10, 2017 · 2 comments
Open

Comments

@alkemann
Copy link

https://github.com/Swagger2Markup/swagger2markup uses this project to parse swagger and according to the dev of it ( @RobWin ), it does not get this attributed, is it possible that this parsers missed it?

It is not required field, but included in the spec : https://swagger.io/specification/#securityDefinitionsObject

@fehguy
Copy link
Contributor

fehguy commented Jul 10, 2017

Seems possible. If you could please provide a test specification, we can add it to the regression testing and see about a fix. A PR (even if broken) would be great.

@alkemann
Copy link
Author

Here is an example of a spec that has descriptions on the security doc https://gist.github.com/alkemann/455643145fafae99bdf49fcd502fb706

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants