You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue arises when trying to use a nested liveview inside a parent live component and that liveview itself has children live components.
The assign updates made in event handlers in the parent live component will run but will not cause the page to update.
When running the Example App in the file, you'll notice that when clicking on the + button for every live view/component that the number updates, except for the Parent Live Component.
If you look for UNCOMMENT: and uncomment another live component inside the Nested Liveview, you'll notice that the Child Live Component no longer updates the page too.
If you comment both live components inside the Nested Liveview, everything will work normally.
My current assumption is that for each live component you add inside the nested liveview, one of the live component parents of the nested liveview will have this problem(From parent to child in order).
The problem never arises in Live Views but only in Live Components.
Expected behavior
Adding Live components inside the nested Live view should not cause its live component parents to stop updating the page when their assigns change through an event handler.
The text was updated successfully, but these errors were encountered:
Environment
Actual behavior
File App to reproduce the behavior: https://github.com/dalideco/bug-liveview-inside-livecomponent/blob/master/main.exs
The issue arises when trying to use a nested liveview inside a parent live component and that liveview itself has children live components.
The assign updates made in event handlers in the parent live component will run but will not cause the page to update.
Parent Live Component
.UNCOMMENT:
and uncomment another live component inside theNested Liveview
, you'll notice that theChild Live Component
no longer updates the page too.Nested Liveview
, everything will work normally.My current assumption is that for each live component you add inside the nested liveview, one of the live component parents of the nested liveview will have this problem(From parent to child in order).
The problem never arises in Live Views but only in Live Components.
Expected behavior
Adding Live components inside the nested Live view should not cause its live component parents to stop updating the page when their assigns change through an event handler.
The text was updated successfully, but these errors were encountered: