OpenAPITools / OpenAPITools/openapi-generator
[REQ] Kotlin ApiClient creates its own HttpClient instance, this is not well suited if used on the server
Nobody has claimed this yet.
- 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.
When using the generated client on the server, creating HttpClient on every request is expensive, ideally we would like to inject the instance of HttpClient ourselves and keep the ApiClient simple.
Describe the solution you'd like
A template that allows for injection of HttpClient would be ideal
Describe alternatives you've considered
There is a way to pass in the engine (OkHttp) for example, but this solves only part of the problem
@jimschubert
@andrewemery
@alisters
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 Kotlin generated ApiClient template and examining how it currently creates HttpClient instances and accepts an engine. Define the injection approach for a caller-provided HttpClient, then verify that generated clients can reuse that instance without creating one per request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, openapi
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100