swagger-api / swagger-api/swagger-ui
Switching Spec, still submit old value in Form Data
Open
Nobody has claimed this yet.
type: bug
- 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: Window
- Browser: chrome
- Method of installation: dist assets
- Swagger-UI version: [e.g. 3.10.0]
- Swagger/OpenAPI version: Swagger 2.0
Describe the bug you're encountering
I have 2 Specs that contains same api, but different enum values
First I tried with one, and then I tried with the second one, and the value of form data is still the old value from the first one, even the dropdown display correctly
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 in Swagger UI with two Swagger 2.0 specs that share an API but define different enum values, switching from the first spec to the second. Trace the form-data submission and compare the submitted value with the second spec's displayed dropdown value; done means the current spec's enum value is submitted.
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
- 35/100