Constructors about mixin HOT 6 CLOSED

Under no circumstances should you add values to an existing enum, for the same reason as we don't use enums in the API. See this article which talks about doing it with reflection but ultimately the reasons are the same.

You cannot instance a mixin because a mixin isn't a class, it only makes sense in terms of its target, and in this particular scenario creating additional instances would be bad.

The recommended way of handling custom "constructor" logic would be to mix in a onConstructed hook using an injector, then do your custom logic there. It's not possible to add constructors to a target class using a mixin for obvious reasons.

If you're talking about creating "extra" [pseudo-enum] instances of your mixin, then the optimal solution is to have a surrogate class which also acts as a target for the mixin, and provides the additional values.

from mixin.

Ah, why would I add the surrogate class instead of just using the surrogate class and no mixin?

from mixin.

Because a surrogate allows you to reuse the code that you're mixing in to MapColour:

It's just an example of what's possible. I have no idea what your goal is so these are just random suggestions as to what you can try.

from mixin.

@modwizcode Do you need further assistance with this or can I close this issue?

from mixin.

from mixin.

Ok cool, re-open if any further related queries.

from mixin.