Introduce relationship queries.#246
Merged
Merged
Conversation
Currently only applies to filtering archetypes only but can be extended to support per entity filtering.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Objective
Introduce a relationship query system that enables traversing entity relationships (e.g. parent–child trees or arbitrary graphs) in both breadth-first and depth-first order. This provides a generic and reusable foundation for hierarchical and graph-based entity systems, with strong type safety.
Solution
VisitEntitiesinterface: Provides a consistent contract for traversal across relationship types through thevisitmethod.Must be implemented by relationship components e.g (e.g.Children,Parent,Neighbour)RelationshipQuery: Accepts aWorld, a relationship type (e.g.Children), an optional target type (e.g.Parent), and optionalData/Filterparameters.Can be used to traverse relationship edges in breadth first or depth first order.RelationshipQuerywhich verifies traversal correctness across multiple topologies:Tests assert that traversal order and coverage match expectations for BFS and DFS.
Showcase
A
RelationshipQuerycan be used to walk hierarchies and a graphs consistently:This makes hierarchical propagation (e.g. transforms, constraints) and graph traversals (e.g. connectivity, influence spreading) straightforward and safe across entities.
Migration guide
These changes do not break existing code however:
ChildrenandParent) should now implementVisitEntities.RelationshipQuery.treebfsorRelationshipQuery.treedfs.RelationshipQuery.graphbfsorRelationshipQuery.graphdfs.Checklist