fix: ensure correct parent effect is associated with render effects #13274
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.
Fixes #13251.
When we invoke
$effect
s in a component, we defer them so that we have child -> parent sequencing. However, this doesn't take into account the fact an$effect
might have been created inside another nested$effect.pre
or template effect – in which case, we incorrectly associate the$effect
with the component's effect rather than the correct$effect.pre
or template effect. So this adds support for knowledge of the parent.