mikesax
Is socket-based navigation on LiveView's roadmap?
On a Rails/Turbo site, the first page is typically loaded using http GET and then sockets are used navigate and replace HTML content for the remainder of the session.
LiveView is amazing for interacting within a page but I find that having a GET request when switching pages can make the experience a bit less smooth.
So I’m wondering… is it on the roadmap for LiveView to handle not only patches but also navigation requests purely over sockets?
Most Liked
rhcarvalho
That’s how it works today!
You can do patches within the same LV, navigate through the socket between LVs and do full page loads to other parts on the app (non-LV).
steffend
This was already implemented years ago ![]()
Basically you’ll want to use <.link navigate=…> or <.link patch=…> instead of href (or the corresponding push_navigate/push_patch functions). Also, the LiveViews you’re navigating between should be part of the same live_session.
steffend
You‘re too fast! ![]()
Popular in Proposals: Ideas
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









