We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
see OAI/OpenAPI-Specification#14 (comment)
empty security object is not getting parsed
"security": [ {}, {"oauth": […]}, {"token-1": []}, {"token-2": []} ]
parsed has only 3 elements
The text was updated successfully, but these errors were encountered:
fixing parsing of empty securityRequirement - refs #492
ad9d80c
Merge pull request #615 from swagger-api/bug/empty-security#492
c1c5af8
Hi @Daxten, Thanks for the report, please checkout if this fixes the issue in branch 2.0
Sorry, something went wrong.
Hi, @Daxten please let us know if it's still an issue
gracekarina
No branches or pull requests
see OAI/OpenAPI-Specification#14 (comment)
empty security object is not getting parsed
parsed has only 3 elements
The text was updated successfully, but these errors were encountered: