I did hit this, so now just use:
<.simple_form for={@form} action={~p"/"} >
instead of
<.form for={@form} action={Routes.home_path(@conn, :action, params)} >
and the :action from verified_route is whatever you defined in the router for that path
I see that people resurrected this thread with the release of Phoenix 1.7. So, probably, I should provide a final solution to it.
What I ended up doing is explicitly re-add search params to the new path when updating the page number:
And I do not re-add the page number when the search is updated because I want to get the user to the first page when they change the parameters anyway.
So, this solution is a bit messy (because the pagination component must know about all other components that change the page parameters, which is a good example of bad coupling) and you should avoid doing that in big projects. That was good enough for a small pet project, though.
People here (@cmo and @Sleepful) say that in Phoenix 1.7 verified routes should preserve GET parameters. I can’t check it right now (the project is still on Phoenix 1.6), so I’ll mark it as the answer. Feel free to drop a message in the thread if it doesn’t work for you.
That’s how I do it even now but I really wonder if there’s a better way now. That and I keep params in the assigns, but it feels dirty.