Merged
Conversation
In order to manually curate trees of effection scopes, you need to be able to specify a parent scope that delimits the lifetime of a scope when you are creating it. V4 has this capability out of the box. This backports the functionality from v4. Internally, a refrenence to the `Frame` object that the scope wraps is maintained. Then, when a scope is passed in, we unwrap the frame and link it up with the parent. As a nice bonus, you can now inspect context values from the debugger when you have a reference to the scope.
taras
approved these changes
Apr 15, 2025
taras
added a commit
that referenced
this pull request
Nov 12, 2025
🚛 Backport `createScope(parent)` to v3
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
2 participants
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.
Motivation
In order to manually curate trees of effection scopes, you need to be able to specify a parent scope that delimits the lifetime of a scope when you are creating it. V4 has this capability out of the box.
Approach
This backports the functionality from v4. Internally, a refrenence to the
Frameobject that the scope wraps is maintained. Then, when a scope is passed in, we unwrap the frame and link it up with the parent.As a nice bonus, because it is there on the object (but not the TypeScript interface) you can now inspect context values from the debugger when you have a reference to the scope.