fix: freeze deriveds once their containing effects are destroyed#17921
Draft
Rich-Harris wants to merge 2 commits intomainfrom
Draft
fix: freeze deriveds once their containing effects are destroyed#17921Rich-Harris wants to merge 2 commits intomainfrom
Rich-Harris wants to merge 2 commits intomainfrom
Conversation
🦋 Changeset detectedLatest commit: a549d39 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
Contributor
|
Member
Author
|
/autofix |
1 similar comment
Member
Author
|
/autofix |
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.
Per #17862 (comment), this freezes the value of a derived if it was created inside a parent effect that is now destroyed. This prevents the sort of bug where a derived reads
foo.bareven thoughfoois nowundefined.If the derived is dirty, a warning will be printed.
This PR also gets rid of some weirdness around
derived.parent— it can only ever be anEffect | null, and there's no need forget_derived_parent_effect.Blocked on sveltejs/kit#15533 and a follow-up that switches remote functions to use
$effect.root(since this effectively undoes #17171), hence draft.Before submitting the PR, please make sure you do the following
feat:,fix:,chore:, ordocs:.packages/svelte/src, add a changeset (npx changeset).Tests and linting
pnpm testand lint the project withpnpm lint