I’ve found another work around just now using the metadata field of the live macro in the router.
:metadata- a map to optional feed metadata used on telemetry events and route info, for example:%{route_name: :foo, access: :user}. This data can be retrieved by callingPhoenix.Router.route_info/4with theurifrom thehandle_paramscallback. This can be used to customize a LiveView which may be invoked from different routes.
With a route of:
live "/tabs/a", TabsLive, :index, metadata: %{tab: :tab_a}
live "/tabs/a/:id/edit", TabsLive, :edit, metadata: %{tab: :tab_a}
live "/tabs/a/new", TabsLive, :new, metadata: %{tab: :tab_a}
live "/tabs/b", TabsLive, :index, metadata: %{tab: :tab_b}
live "/tabs/b/:id/edit", TabsLive, :edit, metadata: %{tab: :tab_b}
live "/tabs/b/new", TabsLive, :new, metadata: %{tab: :tab_b}
Then in TabsLive handle_param you can fetch the tab from the metadata specified above by doing:
# I don't think the host really matters here, but not 100% sure
%{:tab => tab} = Phoenix.Router.route_info(AppWeb.Router, "GET", URI.parse(uri).path, "127.0.0.1")
You can then plop the tab in the assign and use it to display/interact the tab component.
This makes it a little less cumbersome in the sense that you don’t need to parse anything specific out of the path by hand. Albeit, the computational work of parsing the URL is the same.