Hentioe
My router:
live "/cities/:id/users", CityLive
I tried the handle_params function but it was never called:
def handle_params(%{"id" => id}, _uri, socket) do
# some code
end
I tried to follow the practice in the chrismccord/phoenix_live_view_example project and still failed (session is always %{}):
def mount(%{path_params: %{"id" => id}}, socket) do
# some code
end
Can see the parameters from the log:

Can anyone tell me what is missing?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
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
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
If your liveview is mounted in the router and is the root one (not nested) it should work with
handle_params. I did use that a few days ago. If that‘s not the case you should be able to supply the param as part of the session data you supply forlive_render.benwilson512
You need to specify path_params as part of the live route session:
Hentioe
I still have not succeeded.
path_paramsis alwaysnil.chrismccord
You can only receive path params via the
handle_params/3callback, and handle_params is only invoked for the root LV. If you are trying to get path params to a child, you need to retrieve them from the root and pass them down to the children via assigns in the parentHentioe
Maybe I misunderstood what? This is the root LV, which is not loaded from the parent LV. I can get the query parameters of the same level LV from
handle_params, but I can’t get the path parameters.The code is at:
https://github.com/elixirchina/community/blob/a86bb0c89bf158ead69d733a9d14a022ec28d6a9/lib/community_web/router.ex#L23
Thanks for the reply from the author!
chrismccord
The params contain the merged path params and query param so “id” should be there. Can you provide the entire LV?
Hentioe
I made a mistake, sorry! A very small mistake! This problem is invalid
Hentioe
This problem does not exist because I wrote the wrong number of
handle_paramsparameters.Thank you all

homanchou
I too am tripped up by this. Maybe the GitHub - chrismccord/phoenix_live_view_example · GitHub for CRUD user are out of date and need to be updated?
For example on: phoenix_live_view_example/lib/demo_web/live/user_live/show.ex
will break on localhost:4000/users/1 with error:
no function clause matching in DemoWeb.UserLive.Show.mount/2because the received first arg%{}can never match%{path_params: %{"id" => id}}If the recommendation is to now use handle_params/3 to get the path_params, (which handle_params/3 is called sometime after mount/2) does that mean that it is not possible to fetch the User data in mount/2 for the first render?
tme_317
Hi @homanchou,
Yes the CRUD user example is out of date. This working unmerged PR addresses it by using
handle_params/3to get the user by id instead ofmount/2: Get users demo working again by moxley · Pull Request #45 · chrismccord/phoenix_live_view_example · GitHub