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

security not parsing "none" (branch v1) #1305

Open
wsalembi opened this issue Jan 22, 2020 · 0 comments
Open

security not parsing "none" (branch v1) #1305

wsalembi opened this issue Jan 22, 2020 · 0 comments

Comments

@wsalembi
Copy link
Contributor

wsalembi commented Jan 22, 2020 •
edited

Same as #492 bug already resolved in v2

empty security object is not getting parsed

"security": [
{},
{"oauth": […]},
{"token-1": []},
{"token-2": []}
]
parsed has only 3 elements
wsalembi added a commit to wsalembi/swagger-parser that referenced this issue Jan 22, 2020
@wsalembi
swagger-api#1305 fixing parsing of empty securityRequirement
01ec1b9
wsalembi added a commit to wsalembi/swagger-parser that referenced this issue Jan 22, 2020
@wsalembi
swagger-api#1305 fixing parsing of empty securityRequirement (use emp…
d8385f4 
…ty map instead)
gracekarina added a commit that referenced this issue Jan 31, 2020
@gracekarina
Merge pull request #1306 from wsalembi/issue-1305
c3949ab 
#1305 fixing parsing of empty securityRequirement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wsalembi