OpenAPITools / OpenAPITools/openapi-generator
[REQ] A way to specify for generated code destination package
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 you have a lot of models it would be nice to organize them in package/subpackages.
Describe the solution you'd like
A solution would be to somehow be able to specify to each model/api a destination package
Describe alternatives you've considered
Alternative is to break the yaml spec file into smaller ones and to use the generator with target paths as configuration. This approach would mean also (if models are used from one file to another) to add imports mapping. Not that a good alternative but it works.
Additional context
If you have like 100 models it would be nice to have it organized into packages/subpackages, common packages, etc.
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
The issue names no files, tests, or entry points. Start by locating generator configuration and model/API package handling; done means each model or API can specify a destination package while references across files continue to resolve without requiring split specification files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100