swagger-api / swagger-api/swagger-parser
security not parsing "none" (branch v1)
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 867
- Forks
- 560
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing branch v1 with the behavior described as already resolved in v2 and issue #492. Reproduce the provided security array and verify that parsing preserves the empty security object, so the parsed result contains all four elements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100