Brent Roose

No, but we really need the mixin approach.

Because mixins prevent the duplicate class issue, and because we use class doc comments for other stuff as well, so we can't override them every time we generate new model...

> ->value doesn't seem to give the more specific type If that isn't the case, I don't think there's enough value in adding this feature. How come it doesn't work?

Another consideration: `string|int` should still be supported as well, I believe the correct typehint should be `TEnumValue|string|int`. Also I prefer to use `T`, it's shorter and a general accepted convention...

I was under the impression that `@template` doesn't work in phpstorm if you have psalm inspections disabled, maybe I missed them adding native support?

I must admit I haven't used the psalm inspections in PhpStorm because it's too slow for my likings, so maybe @AAllport should provide some input :) I'm fine adding the...

Looking good, only two minor remarks. I think these traits offer enough value to keep the package alive for now :)

What would you call the interface?

Then you'd only be able to implement the interface if you use all traits. I'm fine with that simplicity, but why not combine all traits into one as well then?

I understand what you're trying to do, but could you nevertheless provide a description for future reference? I'm also not a big fan of the `Helper` class. I wonder if...