OpenAPITools / OpenAPITools/openapi-generator
[REQ][Dart] Refactor templates dirs: dart -> dart1-option and dart2 -> dart
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 found it confusing at first when I wanted to make modifications to the dart generator that the dart folder refers to dart1. Also it wasn't clear to me that there was a single dart generator with dart1 and dart2 options.
Describe the solution you'd like
I think logically it would make more sense to have the 'dart' templates using the current version of Dart and refactor the dart1 option into a folder called something like 'dart1-option'.
Describe alternatives you've considered
Remove the Dart1 option - personally I would be all for this but I get that there may be reasons to continue to support Dart 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
Start by locating the Dart generator and its dart and dart2 template directories, then trace how the dart1 and dart2 options select those templates. Rename the directories so dart represents the current Dart version and dart1-option represents the legacy option, updating references while preserving both options. Done means the generator still supports the intended Dart versions and no old directory references remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100