swagger-api / swagger-api/apidom
OpenAPI 2.0/3.x.y - semantic highlighting does not always work for responses
Open
@robert-hebel-sb is already working on this.
Since Jun 30, 2025.
bug
OpenApi 2.0
OpenApi 3.0
OpenAPI 3.1
- Dominant language
- TypeScript
- Stars
- 100
- Forks
- 26
- Avg merge
- 14h 36m
- Merged PRs (30d)
- 22
Description
Describe the bug you're encountering
Semantic highlighting is buggy for responses, e.g. it does not work when the default response is the last response defined:
When it is gone or defined as the first response:
Sometimes the highlighting will partially work, e.g. in this case the highlighting will work for every response expect for the default one, as well as the 200 key:
To reproduce...
Steps to reproduce the behavior:
- Go to https://editor-next.swagger.io/
- Load the OpenAPI 3.0 or 3.1 example
- Scroll through the definition to see responses for different operations
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.
Assessment
This issue has not been assessed yet.