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
Many types in LDtk have an Iid, and I think it's becoming increasingly useful to create components storing these values on the corresponding entities. This is being done for LevelIid and EntityIid currently. However, these two implementations are pretty different, when they could be pretty much exactly the same type with a slightly different context.
Instead we could have a generic LdtkIid<> component and contextualize it with a generic parameter. Something like...
Many types in LDtk have an Iid, and I think it's becoming increasingly useful to create components storing these values on the corresponding entities. This is being done for
LevelIid
andEntityIid
currently. However, these two implementations are pretty different, when they could be pretty much exactly the same type with a slightly different context.Instead we could have a generic
LdtkIid<>
component and contextualize it with a generic parameter. Something like...This would reduce repeated code and make it easier to add other Iid components in the future
The text was updated successfully, but these errors were encountered: