Trying to do something like. some_route = "foo/bar" ~p"#{some_route}" Aside from the fact the compile checker complains, the / in between foo and bar gets escaped inside the ~p somewhere so the request ends up crying that foo%2Fbar can be found. I realize this has everything to do with escapable …

I got it, I should pass a lambda instead of assigning a rendered value to the patch assigns. Then call into that lambda at run time. I bet it has to do with the way the call to ~p is composed. This way I can pass the ~p"/admin/posts" correctly at the time I define ~p. Also remember the warning is at…

I believe you can do: foo = ~w[foo bar] dbg ~p"/#{foo}"

Thoughts about compile time warnings? My CI is not gonna like it. And maybe this is just not the best pattern to follow.

What does the warning say exactly? I’m also interested in what trouble you’re having with deriving params to use slug. How are you doing it? I current have a project where pretty much everything has a slug and doing somewhat similar to you except that I push_redirect after an update. You can alw…

warning: no route path for MorphicProWeb.Router matches "/#{socket.assigns.patch}/#{post.slug}" lib/morphic_pro_web/live/admin/post_live/form_component.ex:74 So basically after I made the assignment to patch. |> push_patch(to: ~p"/#{socket.assigns.patch}/#{post.slug}")} I’m not doing much oth…

Actually I just checked and I push_patch and it works fine even with a changing slug. What is the value of socket.assigns.patch? It’s saying your route doesn’t exist which is ~p doing its job! Are you sure socket.assigns.patch isn’t nil or something?

path = ~p"/#{socket.assigns.patch}/#{post.slug}" IO.inspect([socket.assigns.patch, post.slug, path], label: :WTF) Renders at run time correctly but at compile time I see the warning. If you wanted to try this I’m mostly working on a default generated form. So at assignment in the sh…

My only guess would be that that it’s another live component that is throwing that error—that’s usually what it it is for me when I get super stuck thinking a variable is definitely populated and it’s not :sweat_smile:

Correct. The point of verified routes is to verify the routes at compile time, which it cannot in your case. In your case, you can build the route yourself, as a string without the sigil, since verified routes is not giving you anything, or be less dynamic and pass the route ~p as parameter …

Elixir Programming Language Forum

Phoenix Verified routes and escaping URI

Questions & Help Questions

polypush135 April 2, 2023, 9:03pm 3

Thank you that did it.