I have requested a on_unmount callback in the “Suggestions” section, but it does not seem to catch! 
Lets hope there will come something! 
mortenlund
1
DGollings
Just now implemented connected_component.ex from the demo and with the patches suggested by @mortenlund .
Looks like an excellent solution to me, did exactly what I needed it to and saved me several screens worth of boilerplate handlers.
Apart from wondering why this is not part of Phoenix itself maybe you could release it on Hex? Would be cleaner than a random ‘lib module’ in our codebase
Thanks again
1
mortenlund
I have made a new revision of this whole approach where i use telemetry messages that Phoenix sends when a live_component is removed.
This was suggested in the forum.
I will concider making this a library as it really simplifies and containerize the components.
If we could assign values using render_live in a way where the assigns never gets encoded but actually used by the new process we would not need this.
Live_view can read the assigns from the parent using assign_new but the docs states that this is not to be relied on
0
DaAnalyst
Using assign_new/3 for such purpose is unreliable.
From the docs:
”Assigns sharing is performed when possible but not guaranteed. Therefore, you must ensure the result of the function given to assign_new/3 is the same as if the value was fetched from the parent. Otherwise consider passing values to the child LiveView as part of its session.”
* not guaranteed: less likely than not
With nested LiveViews sending messages from one process to another is the only reliable + flexible way. The alternative is to simply call the parent from its child (say, to fetch its assigns) with the likes of the following which is what I do in certain occasions in my nested LVs setup:
GenServer.call( parent_pid, { :fetch_assigns, keys})
If LiveComponents are supposed to manage their own state (as in independently fetch data and communicate with each other) then send_update/3is the only feasible way long term.
0
jtormey
Could you share how you’re using telemetry messages to unmount the component? I like that idea much more than using phx-remove in the template.
0