swagger-api / swagger-api/swagger-ui
Swagger UI doesnot work if we more parameters in the Operation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A (please complete the following information)
- OS: macOS
- Browser: both chrome and safari
- Version: all
- Method of installation: dist assets
- Swagger-UI version: 3.10.0
- Swagger/OpenAPI version: OpenAPI 3.0
Content & configuration
Swagger UI does not work if we more parameters in the Operation annotation.
In Chrome, It works only if we have one Parameter and fails if we have more than one Parameter.
In Safari, it works upto 3 Parameters and fails if we have more than 3 Parameters.
Example Swagger/OpenAPI definition:
# your YAML here
Swagger-UI configuration options:
SwaggerUI({
// your config options here
})
?yourQueryStringConfig
Describe the bug you're encountering
To reproduce...
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
Screenshots
Additional context or thoughts
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 issue with Swagger UI 3.10.0 and an OpenAPI 3.0 definition containing multiple operation parameters, using the supplied dist assets in Chrome and Safari. Compare the behavior with one, three, and more parameters. Done means the operation renders and remains usable with multiple parameters in both browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100