swagger-api / swagger-api/swagger-parser
Allow to provide own `RemoteUrl` implementation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 867
- Forks
- 560
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Description
In essence we would like to be able to control how the HTTP requests are sent (e.g. handle custom authentication, connection settings, outgoing proxy, timeouts, rate limiting, …).
We are happy to contribute the changes necessary, once decided what's the best way to achieve this.
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 locating the Java code that defines or invokes the RemoteUrl implementation and trace how HTTP requests are sent. Review the available request configuration and determine the intended extension point for custom authentication, connection settings, proxies, timeouts, and rate limiting. Done means the agreed design is implemented and covered by relevant request tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100