OpenAPITools / OpenAPITools/openapi-generator
[REQ][rust] Trait based implementation for `reqwest`
Open
Nobody has claimed this yet.
Enhancement: Feature
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
Trait based API is much more convenient than functions-based.
Describe the solution you'd like
Introduce traits and structs for API methods in reqwest implementation as it realized in hyper implementation.
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 comparing the existing reqwest implementation with the hyper implementation mentioned in the issue. Define the traits and structs needed for the reqwest API methods, then verify that generated Rust clients use the trait-based interface consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100