In design, swagger 2.0 + yaml + operationId with uppercase = no request generation
- Dominant language
- TypeScript
- Stars
- 40k
- Forks
- 2.4k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
### Expected Behavior
In design mode, with swagger 2.0 in yaml, if i set an operationId value with uppercase, insomnia create the request in debug when i click on generate request collection.
### Actual Behavior
In design mode, with swagger 2.0 in yaml, if i set an operationId value with uppercase, insomnia dont generate the request in debug. I have to set the value in lowercase and it work.
### Reproduction Steps
- Create new design document
- Paste this :
swagger: "2.0"
info:
title: Sample API
description: API description in Markdown.
version: 1.0.0
host: api.example.com
basePath: /v1
schemes:
- https
paths:
/users:
get:
operationId: getUsers
summary: Returns a list of users.
description: Optional extended description in Markdown.
produces:
- application/json
responses:
"200":
description: OK
- Click on generate request collection
No request generated.
- Change operation id to getusers
- Click on generate request collection
Request generated
### Is there an existing issue for this?
- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.
### Additional Information
_No response_
### Insomnia Version
2022.7.5
### What operating system are you using?
Windows
### Operating System Version
Windows 10 Professionnel 22H2
### Installation method
Installer on website insomnia + auto update insomnia
### Last Known Working Insomnia version
_No response_
Contributor guide
Research direction
Start with design-mode Swagger 2.0 request collection generation and reproduce the issue using the YAML example with operationId set to getUsers. Compare it with the lowercase getusers case; done means the uppercase operationId generates the request collection successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100