swagger-api / swagger-api/swagger-ui
Providing INFO about HTTP Request before it's made
Open
Nobody has claimed this yet.
cat: user experience
needs: UX/design input
type: enhancement
version: 4.x
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
When executing the HTTP Request, it is not really obvious what will be the properties of HTTP Request that will be executed. Most significant property is URL. SwaggerUI should probably make this information visible for UI consumer to indicate what will be the actually requested URL.
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 an HTTP request in Swagger UI and trace where the request is prepared before execution. Identify the UI entry point that can expose the actual URL and other request properties before sending; done means the consumer can review those properties before the request is made.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100