Never. We’re talking about how best to introduce live connection cancellation. My proposal is to never cancel, but be explicit about when you want to connect. Basically have a load function that works as mount before connection then live that works as mount post connection. The nice thing here is that on pages with no live function they function exactly like a single file controller, similar to a svelte file, where I can have my markup, my page load, and page updates all in one file. This is a nicer DX for regular dead pages than what we already have. It has the added benefit of allowing one to even defer the connection until later (call live/3 at some other point) making pages that are “dead for now”.
To get to your question however what I’m proposing is since we can now (in my theoretical universe) render “dead” pages like LiveViews, we can allow renders of any “dead” content like json. I just took the calling convention from LiveView native instead of ~SWIFT I chose ~JSON
