Add Apecs.Experimental.Children module #132
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds
Apecs.Experimental.Children
to support one-to-many relationships. A "parent" entity may have multiple values of a particular component type. This is like how inapecs-physics
an entity with aBody
component value may have many collisionShape
component values (where eachShape
value is owned by another distinct entity), but general-purpose so that we can build this kind of relationship for any component types.There is an example that demonstrates usage and is likely a good starting point to get a feel for what the interface is like.
I'm not totally sure this functionality belongs in the main
apecs
library, though I feel the internals are fiddly enough that it'd be nice saving others from reimplementing similar behavior. I'm finding the functionality useful in my projects, but I could also see the code being pushed into a new library if that's preferred.