swagger-api / swagger-api/swagger-ui
Query parameters and path variables are not read
Open
Nobody has claimed this yet.
type: support
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A
- OS: linux
- Browser:chrome
- Version: 70.0.3538.77
- Method of installation: npm
- Swagger-UI version: 3.20.4
- Swagger/OpenAPI version:"swagger":"2.0"
Not extra configuration used.
To reproduce...
Steps to reproduce the behavior:
- Go to main page
- Click on any service
- Click on 'try it out' and complete a query parameter or path variable
- Click on execute
- See query parameter or path variable is not in generated curl and not used to call service and input field is empty.
Expected behavior
parameter or path variable is in generated curl
Before execute
After
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
Reproduce the problem in Swagger UI 3.20.4 with a Swagger 2.0 service by using Try it out with a query parameter or path variable. Trace the request and generated curl handling, then verify that the entered value appears in the curl command and is sent to the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100