swagger-api / swagger-api/swagger-parser
v3 parser does not always consider extensions
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 867
- Forks
- 560
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Description
OpenAPIV3Parser currently only takes extensions into account when the OpenAPI read methods are used.
It should also consider extensions in e.g. the SwaggerParseResult readContents method.
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 with OpenAPIV3Parser and compare how extensions are handled by the OpenAPI read methods versus SwaggerParseResult.readContents. Confirm the expected behavior from the existing read paths, then ensure readContents also considers extensions and verify the parser behavior with the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100