OpenAPITools / OpenAPITools/openapi-generator
[REQ] Feature Request Description
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.
I have to take the same yaml file and produce the client and server endpoints and create a straight through spring boot service. So if I call get /getPet against the SB service, it will then call /getPet. So server endpoints -> @Controller -> @Service -> client resttemplate.
It is quite tedious to setup the @Service layer to accept the call from the @Controller to in turn call the Resttemplate later.
Describe the solution you'd like
OpenAPITools already generates the server and client code from a single Yaml file. It would be great if it could (if from same yaml file) generate the tie up code as well thus creating a straight through service.
Describe alternatives you've considered
Alternative now is to roll up sleeve and hook up 100 endpoints.
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
No files or tests are named. Start by reviewing the existing Spring Boot server and client generation paths, then determine how one OpenAPI YAML file could produce Controller-to-Service-to-RestTemplate wiring for every endpoint. Done means the generated service forwards calls from generated server endpoints to the generated client without manual hookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100