blset
Live layout assigns available but not @socket.assigns
Hello,
when using a live route with url put in assigns by handle_param callback like so
def handle_params(params, url, socket) do
socket = assign(socket, :url, URI.parse(url))
{:noreply, socket}
end
inside the live layout @url is available but surprisingly @socket.assigns is consistently #Phoenix.LiveView.Socket.AssignsNotInSocket<>
what is the explanation of this counter intuitive situation ?
Thanks
Best regards
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked
axelson
You get that "error’ because that is not the correct way to fetch assigns (as mentioned by @LostKobrakai). Previously there were docs for that module that clarified some more (but it looks like they’ve been removed after 0.15.1): Phoenix.LiveView.Socket.AssignsNotInSocket — Phoenix LiveView v0.15.0?
LostKobrakai
Not using
@nameto fetch data breaks change tracking of liveview, so@socket.nameis made to raise an error.Last Post!
blset
ok it’s related to change tracking and it is kind of a warning. But AssignsNotInSocket is a paradoxal message, since there are assigns in the socket
also @socket.name is made to raise an error, but is it the case for @socket.assigns.name ?
also inside the live module different handlers you can use socket.assigns.name to get the value or pattern match
would it be any clearer change the message to something like AssignsNotAddressableThisWay in the templates ?
Thanks
Best Regards