swagger-api / swagger-api/swagger-parser
SwaggerParse Results need to refactor
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 867
- Forks
- 560
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Description
SwaggerParseResults.. should show what are the warnings and errors, by some prefix or separate list like in ParseRoot..
Please help to fix.
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
Locate SwaggerParseResults and ParseRoot in the Java parser sources, then read how warnings and errors are currently represented and exposed. Compare the existing ParseRoot presentation and define completion as SwaggerParseResults clearly separating or prefixing warnings and errors; the issue names no tests, so identify the relevant parser tests before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100