Transition to Enum classes #271
luchfirearmland
started this conversation in
Ideas
Replies: 1 comment
-
Hi! I agree that using Enums for states would be a great improvement, especially for reducing the number of files and making the API more streamlined. However, since this package still supports PHP 7.4 and PHP 8.0, introducing Enums as the default might be a breaking change. A possible approach could be introducing Enums as an optional feature while keeping the current implementation for backward compatibility. That way, users on PHP 8.1+ can take advantage of Enums, while others can continue using the existing approach. Would love to hear the maintainers' thoughts on this! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, guys!
Long time user of this package. I think it is high time for this package to be upgraded to use Enum classes as the default way. I've been utilizing Enum a lot lately. When I went back to codes related to states, I feel like this package should have been created in an Enum-first way to reduce the number of files that needs to be created.
I believe you've been thinking about this as well. It feels off not to think of Enum class when thinking of a state of a model.
I hope you can give time to respond to this idea of mine. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions