swagger-api / swagger-api/swagger-codegen
[Rust] Allow to choose client library between hyper and reqwest
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Rust client codegen uses hyper library. This library is "low-level", and requires some tunning (to deal with https, for example).
Reqwest alternative https://github.com/seanmonstar/reqwest (which uses hyper under the hood), seems to be a good alternative.
Swagger-codegen version
master
Swagger declaration file content or url
Not applicable
Command line used for generation
Not applicable
Steps to reproduce
Not applicable
Related issues/PRs
Not found
Suggest a fix/enhancement
PR in preparation.
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 Rust client code-generation templates and the current hyper integration, then review how client-library choices are exposed during generation. Done means generated Rust clients can select either hyper or reqwest while preserving the existing hyper option. The issue notes that a PR was in preparation, so check for overlapping work first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100