I’d like an overview of how LiveView’s supervision tree works when you have nested LiveView components.
Or What’s the general architecture in a nutshell?”
Each liveview is a single process, no matter how many nested components it has.
1 Like
with phx target we have parent and myself. is it possible to send it to children?
how do i carry out comm b/w nested live view components
There are multiple sections in the documentation dedicated to this: Phoenix.LiveComponent — Phoenix LiveView v1.0.7
2 Likes
One way to visualize the supervision tree/processes would be to connect an Observer to a live app.
Another idea is to run a minimal Phoenix app inside of LiveBook and use its process visualizations.
