OpenAPITools / OpenAPITools/openapi-generator
[REQ] Allow us to transform model names via config
Open
Nobody has claimed this yet.
Enhancement: Feature
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
I have a situation where a the dart-dio-next generator is generating MyEnum in three different places, which is creating namespace conflicts. Would be nice if we could map model names such as
WebhookDetails.MyEnum => WebhookDetails.MyEnum2
UserDetails.MyEnum => UserDetails.MyEnum3
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 at the dart-dio-next generator entry point and trace how model names are derived and configured. Review existing configuration options before defining how mappings such as WebhookDetails.MyEnum to WebhookDetails.MyEnum2 should be accepted and applied; done when distinct configured model names are generated without namespace conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100