feat: method componentsAtPoint
now reports the "stacktrace" of points
#1615
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.
Description
The method
componentsAtPoint
now has an optional parameternestedPoints
, which will record the "stacktrace" of points up to and including the currently returned component. This allows for better flexibility in understanding the point's position relative to its parent and the world. This also allows the methodcomponentsAtPoint
to return an iterable ofComponent
s instead of an iterable ofComponentPointPair
s.Checklist
fix:
,feat:
,docs:
etc).docs
and added dartdoc comments with///
.examples
.Breaking Change
componentsAtPoint()
. However, since the method itself was only introduced 2 weeks ago (feat: Added componentsAtPoint() iterable #1518), and there hasn't been a Flame release since then, the change can be considered non-breaking.Related Issues
Closes #1592