socket = socket
|> assign(:results, search_results(socket.assigns.query))
|> assign(:loading, false)
make the debounce do its job better?
Argument being that expensive searches might last 1-200ms and in the meantime a new keystroke would appear
Actually the two implementation are the same because the assign function does not change socket in place, but build a new copy. The new socket is sent to the live view only when handle_info function completes.
Search_results in my implementation is a synchronous call and blocks the process until it returns. If search_results takes a very long time what happens is that the updated query terms queue in the mailbox of the process until the search_results function returns. You can see it very well if you put something like Process.sleep(10_000) inside the search_function.
I'm a 12-year ruby veteran - and still breaking in my elixir-shoes
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.