Brian Cardarella

@josevalim I think we're arguing for the same things here. For example, here is what Alpha's project structure looks like: In the context of this application, the "Live" module doesn't...

> PS: I'm gone for the day No need to reply immediately, I don't want to lose my state of mind so I'm going to provide my replies right now....

I have a working proof of concept now: https://github.com/user-attachments/assets/69f5ae14-0a4f-429e-a7e9-263d158bb595 This is a React application who's state is being managed by a LiveView endpoint. That endpoint emits JSON in the dead...

> Can you please explain the rationale for doing the initial HTTP fetch? This is for front-ends that wouldn't be rendering the HTML from Phoenix. I presumed all of the...

> Therefore, if LiveView needs a dead render to work, and LiveJSON doesn't, then that's something else we need to make customizable, which will factor into the trade-offs and the...

The reason why I punt in the rendered function is to avoid this check: https://github.com/phoenixframework/phoenix_live_view/blob/main/lib/phoenix_live_view/renderer.ex#L74 The `Phoenix.LiveView.Rendered` struct is change tracking in a way that makes sense for markup but...

thank you, I'll work from this. I'm planning to do so this weekend. If I develop a PR do you want me to PR your branch?

`conn` is the `Plug.Conn` struct and is usually in your controller, what you're showing are routes. Can yo ushoudl the controller? The stack trace you pasted shows the specific file:LOC

And very welcome maintenance 😄

@tobiasdroessler there isn't one I'm aware of. Is there something specific you're trying to implement?