Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Jetpack Compose version: 1.3.0-alpha04 Jetpack Compose component used: UI
Consider the following
DelegateableNode
instances.If I try to read
foo
usingModifierLocalFoo.current
in aDoFooNode
that:UseFooNode
delegates toUseFooNodeInASpecificWay
also delegates to that instance ofUseFooNode
a circular dependency is introduced because
ModifierLocalModifierNode
depends on the implementation ofvisitAncestors
which has this line:In the case of
DoFooNode
with 2 layers of delegation:node
will point toUseFooNode
.node.parent
will point toUseFooNodeInASpecificWay
.UseFooNodeInASpecificWay.providedValues
is called it will delegate back to its instance ofDoFooNode
which is the callingDoFooNode
.DoFooNode
thusly returns its ownprovidedValues
instead of that of a parentDoFooNode
.