Multiple routes point to the same LiveView, how does the live_path function explicitly get one of them?

Hentioe · October 19, 2019, 5:37am

E.g:

live "/c/:category_id", IndexLive
live "/t/:tag_id", IndexLive

Use the live_link to navigate:

<%= live_link “Hello”, 
           to: Routes.live_path(@socket, BlogWeb.IndexLive, 10001) %>

As above, only paths with a link of /c/10001 can be generated. How do I choose to generate the /t/10001 path?

preciz · October 19, 2019, 8:43am

Have you tried with the :as option?

live "/c/:category_id", IndexLive, as: "c_route"
live "/t/:tag_id", IndexLive, as: "t_route"

github.com

phoenixframework/phoenix_live_view/blob/master/lib/phoenix_live_view/router.ex#L32


        [:user_id, :remember_me]


  * `:layout` - the optional tuple for specifying a layout to render the
    LiveView. Defaults to `{LayoutView, :app}` where LayoutView is relative to
    your application's namespace.


  * `:container` - the optional tuple for the HTML tag and DOM attributes to
    be used for the LiveView container. For example: `{:li, style: "color: blue;"}`.
    See `Phoenix.LiveView.live_render/3` for more information on examples.


  * `:as` - optionally configures the named helper. Defaults to `:live`.


## Examples


    defmodule MyApp.Router
      use Phoenix.Router
      import Phoenix.LiveView.Router


      scope "/", MyApp do
        pipe_through [:browser]