swagger-api / swagger-api/swagger-codegen
[JAVA jaxrs] Is there any option to override operations grouping logic while generating apiImpl
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
[JAVA jaxrs]
Is there any option to override operations grouping logic while generating apiImpl.
Grouping of impls is happening based on first of the path param.
Problem we face is, all our APIs' path start with version, for ex: v1/{some dynamic path param}/resource/action. We have around 500 APIs, and 500 methods are generated in single Java file. Is it possible to group the generation based on resource or tags?
Is there any other recommended approach?
Swagger-codegen version
Swagger-codegen version : 2.3.1
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
Begin with the Java JAX-RS apiImpl generation path and the generated Java file described in the issue. Verify how the current first-path-parameter grouping behaves for versioned paths, then define and validate the requested resource- or tag-based grouping or document the supported alternative.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100