I ran into code where one LiveView’s heex is calling another one throughlive_render. While I think this particular code is not optimal, I wonder: Since the introduction of Components and LiveComponents, are there any valid use cases to nest LiveViews?

I could see library authors leverage this.

I’ve wondered the same. I’m still not sure :smiley: [image] LiveComponent vs child LiveView Questions / Help So I wanted to make sure to understand the different tradeoffs between LiveComponents and child LiveViews If you have the need create a component that also needs …

Nested LVs are still useful for failure isolation, individual message passing capabilities and becoming sticky, which live components can‘t. All of those are more niche usecases though.

Yeah being able to make a child LV sticky is what makes it interesting. We use that for UI elements that should persist while navigating between views, like an audio/video player, and a “new post” input box.

I’ve used them for exactly same use-cases. The only thing that I can’t shake off is that there is actually zero support for them and using them feels always like a hack, I mean you can plug in something like PubSub for communication, but still.

Nested LiveViews are very useful when building an app that’s having concurrent mostly-independent yet subordinated (as in children) flows of execution that are otherwise synchronous in nature on their own. The app I am now building has the following setup: a parent LiveView handling shared layout …

I think a really good use case for live_render is 3rd party payment forms, e.g. Stripe/Sumup. If you encapsulate the “payment” flow in its own process, so it can use handle_info for async stuff. This is especially helpful if you are using webhooks to update data.

Any documented examples on how to use sticky liveviews? The documentation is rather sparse.

i think docs need to be more updated

There’s an example in Chris McChord’s live_beats app: live_beats/lib/live_beats_web/components/layouts/live.html.heex at master · fly-apps/live_beats · GitHub And we have a slightly more complex (and still undocumented and quite messy) implementation in Bonfire: sticky child LV in layout sticky L…

What are the valid use cases for nested LiveViews?

Phoenix Forum Questions / Help

tcoopman October 6, 2024, 5:09am 3

I’ve wondered the same. I’m still not sure