swagger-api / swagger-api/swagger-core
[Bug]: duplicate and widening of allowed options
Open
Nobody has claimed this yet.
backlog
Bug
- Dominant language
- Java
- Stars
- 7.5k
- Forks
- 2.3k
- Avg merge
- 18h 1m
- Merged PRs (30d)
- 10
Description
Description of the problem/issue
The documentation that is generated exposes entire enum values and not just allowed values.
Affected Version
e.g. 2.2.51 - but this occurs even in older versions like 2.2.9
Earliest version the bug appears in (if known):
e.g. < 2.2.9
Steps to Reproduce
Checklist
- I have searched the existing issues and this is not a duplicate.
- I have provided sufficient information for maintainers to reproduce the issue.
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 reproducing the generated Swagger/OpenAPI documentation with an enum that has allowed values, as described in the issue. Trace where enum values are collected and compare the generated output with the expected allowed values; done means the documentation contains only the allowed values without duplicates or widening.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100