PrincetonPoh
I thought these 2 implementations are the same.
case Customers.update_customer(customer, params) do
{:ok, new_customer} ->
{:noreply,
socket
|> assign(:customer_form, to_form(Customers.change_customer(%Customer{})))
|> assign(
:customers_list,
Enum.map(socket.assigns.customers_list, fn c ->
if c.id == id do
new_customer
else
c
end
end)
)
|> put_flash(:info, "Customer details updated!")}
{:error, %Ecto.Changeset{} = changeset} ->
{:noreply,
socket
|> assign(:customer_form, to_form(changeset))
|> put_flash(:error, "failed to update customer details")}
end
case Customers.update_customer(customer, params) do
{:ok, new_customer} ->
socket
|> assign(:customer_form, to_form(Customers.change_customer(%Customer{})))
|> assign(
:customers_list,
Enum.map(socket.assigns.customers_list, fn c ->
if c.id == id do
new_customer
else
c
end
end)
)
|> put_flash(:info, "Customer details updated!")
{:noreply, socket}
{:error, %Ecto.Changeset{} = changeset} ->
{:noreply,
socket
|> assign(:customer_form, to_form(changeset))
|> put_flash(:error, "failed to update customer details")}
end
In the above example, I pipe the assigns directly in the {:noreply, socket |> …}. This works perfectly and my socket is updated. HOWEVER, when I place the piping outside of the {:noreply, socket} tuple, the socket does not update. Why is that so?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
thomas.fortes
variables are immutable in elixir, so when you do the piping and everything else you’re executing an statement that has a result of a socket with the assigns, but that’s it, the result isn’t stored anywhere.
Then you do your
{:noreply, socket}and the socket in this line is the socket that is passed to the function as an argument, not the one that you just assigned things.As an small experiment you can try executing these lines in an iex shell:
And see what the last line show for test.
If you want to preserve the result of your operations you can use
But it is important to know that this isn’t changing the variable, but rebinding it.
This link has a nice explanation about what rebinding is.
PrincetonPoh
Ahh, I understand! Thank you for explaining