swagger-api / swagger-api/validator-badge
Validator doesn't enforce uniqueness constraint of operationId
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Java
- Stars
- 227
- Forks
- 81
- Avg merge
- 2h 3m
- Merged PRs (30d)
- 1
Description
The spec defines operationId as optional, however it must be unique. The validator passes specs that violate that constraint today.
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 locating the validator entry point that handles OpenAPI operationId values and inspect how repeated values are currently treated. Add coverage for a specification with duplicate operationId values, then verify that the validator rejects it while still allowing operationId to be omitted.
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
- 35/100