I’m creating a search form with filters and want both the query and the filters to change the URL. The filters and query can be set separately or together, and handle_params can already deal with either being empty. What I’m doing is triggering a push_patch on events (filter click, form submit, cle…

[image] zamith: Alternatively, is there any other design pattern I should be following to set this up? I set up events to do exactly what you’re doing but with a different problem, but I wonder, does it make more sense to use live_patch links from your template with the query params in tact a…

The reason I’m not using live_patch is because both filter and search are independent generic components and I don’t want to have to pass all the assigns to both. Instead, whenever they are “used”, they send the parent an event saying “Hey, someone searched for X” or “Hey, someone filtered by Y”. I…

[image] zamith: Instead, whenever they are “used”, they send the parent an event saying “Hey, someone searched for X” or “Hey, someone filtered by Y”. Would you mind gisting the complete code for those components and how this parent event is sent?

[image] cnck1387: What’s interesting is the --live generator from Phoenix 1.5 includes making a search form using the event style but in their case, they are doing an external redirect so maybe the use case is different. How to try it. I tried generating but no search feature got generated. m…

I’m using Surface, but you can do the same with regular LiveView. https://gist.github.com/zamith/7016275743866c338cfff3b92391f7af Filters.ex defmodule LocalEatsWeb.Live.Restaurants.Components.Filters do use Surface.LiveComponent @filters [ all: "Todos", take_away: "Take-Aw…

I have the same problem. Desperate for a solution… https://forum.elixirforum.com/t/cleaner-push-patch-and-handle-params/35583

Here is how I solved it in my app: I store the params in handle_params as part of the assigns: def handle_params(params, url, socket) do # You could store the params as is but I like to store # only what has been parsed/validated. params = parse_params(params) {:noreply, assign(sock…

for whoever that comes across this thread, @josevalim ’s answer will not apply if you are using actions in your router declarations, as the route helper gets renamed to match the controller, and also results in different helper arities for different helpers. Until the day comes where where we can us…

FWIW, you can also directly use the URI rather than calling the Routes helpers. The above code does this as well, but I wanted to provide a more concise version if you don’t need as many bells and whistles. def handle_params(_params, uri, socket) do {:noreply, assign(socket, :uri, URI.parse(u…

Worth adding that instead of URI.decode_query/1 and URI.encode_query/1, you might want to use more robust Plug.Conn.Query.decode/1 and Plug.Conn.Query.encode/1, which do better encoding/decoding of lists in URL (e.g. ?ids[]=1&ids[]=2). I.e. URI.decode_query("ids[]=1&ids[]=2") # => %{"ids[]" => "2…

LiveView push_patch append to params

Questions & Help Questions

cnck1387 April 25, 2020, 1:08pm 4

Would you mind gisting the complete code for those components and how this parent event is sent?