Add ability to seal enum classes in Dart #81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In a project we have a need to generate sealed classes in Dart but fall back to abstract classes in some cases. This PR adds the ability to configure enum generation by creating an EnumConfig struct and optionally specifying a map of types which should use the specified behavior.
I don't know if this fits into your vision for this project but I figured I'd open this PR and see what you thought as it would be nice to keep parity with this main project.
Test Plan
The default is to generate all code exactly as it has been in the past. The new sealed behavior has to be opted in to.