OpenAPITools / OpenAPITools/openapi-generator
[REQ] [Dart] Use native Dart enums instead of enum classes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Currently enums are implemeted using an outdated enum implmentation using a class with static fields which was necessary when Dart didn't have enums as part of the Language.
But since quite some time we have now simple to use enums. So it would be great to use them instead.
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 the Dart generator templates or entry points that produce enum classes, then determine the affected generated output and its existing tests; done means Dart enums are emitted natively without breaking supported generated clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100