Skip to content

fix: ensure correct parent effect is associated with render effects #13274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 17, 2024

Conversation

trueadm
Copy link
Contributor

@trueadm trueadm commented Sep 17, 2024

Fixes #13251.

When we invoke $effects 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.

Copy link

changeset-bot bot commented Sep 17, 2024

🦋 Changeset detected

Latest commit: ebc685d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@Rich-Harris Rich-Harris merged commit b624380 into main Sep 17, 2024
9 checks passed
@Rich-Harris Rich-Harris deleted the ensure-correct-parent branch September 17, 2024 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nested effect runs twice on state update when wrapped in template effect
2 participants