You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that the interfaces for listeners need to mention the type of the entity/context, and if you have two contexts, you would basically create the same class twice(or more), but each copy would have a different SOMETHINGEntity
Proposition 1:
If more than 1 context, create them as IAnyAppCheeseAddedListener + IAnyGameCheeseAddedListener
Autocomplete will make it very easy to adapt. You could also make this change for 1 context, to put that context name in there always.
Proposition 2:
IAnyCheeseAddedListener< T > where T : Entity
We can't limit it to AppEntity / GameEntity as far as I know as "where T" does not allow A-or-B.
The method that implements the interface would use T
The text was updated successfully, but these errors were encountered:
The problem is that the interfaces for listeners need to mention the type of the entity/context, and if you have two contexts, you would basically create the same class twice(or more), but each copy would have a different SOMETHINGEntity
Example"
[App, Game] //Two contexts
[Event(EventType.Any)]
public sealed CheeseComponent : IComponent {}
Proposition 1:
If more than 1 context, create them as IAnyAppCheeseAddedListener + IAnyGameCheeseAddedListener
Autocomplete will make it very easy to adapt. You could also make this change for 1 context, to put that context name in there always.
Proposition 2:
IAnyCheeseAddedListener< T > where T : Entity
We can't limit it to AppEntity / GameEntity as far as I know as "where T" does not allow A-or-B.
The method that implements the interface would use T
The text was updated successfully, but these errors were encountered: