refactor!: improve RON enum type system #3
Merged
Conversation
This file contains 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
BREAKING CHANGE: Replace rawRonEnum with new ronEnum type using variant-based syntax
- Add new RON enum type handling in generators.nix
- Replace rawRonEnum with ronEnum type for better type safety
- Add ronTupleEnum and ronTupleEnumOf types for tuple-based enums
- Update cosmic-term and config files to use new enum syntax
- Improve merge behavior for RON types
- Update enum usage from `{__type = "raw", value = "X"}` to `{__type = "enum", variant = "X"}`
HeitorAugustoLN
force-pushed
the
enums
branch
from
799380c to
d1cf86c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
BREAKING CHANGE: Replace rawRonEnum with new ronEnum type using variant-based syntax
{__type = "raw", value = "X"}to{__type = "enum", variant = "X"}