Thanks.
I’m curious how this new api works regarding the first server side render. If I understand correctly, rendering the page used to happen immediately after mount/2. Does it now happen after handle_params/3 in order to avoid flash of a blank page on first paint?
This is not the case. handle_params gets called once between the first call of mount and the first call of render.
Hello All,
I found this thread while trying to get params for a “router” liveview.
This has changed very recently (with version 0.6.0) so I put this as a reminder for future readers.
Now it is possible to get params (url ids + querystrings) directly from mount/3 which now accepts params as a first argument, ex :
def mount(%{"id" => id, "token" => token} = params, session, socket) do
....
I think this is the correct way of handling it as of today 
Cheers,
Sébastien.
Useful clarification recently added by Jose when deciding whether to use mount or handle_params
Note the parameters given to
c:handle_params/3are the same as the ones given
toc:mount/3. So how do you decide which callback to use to load data?
Generally speaking, data should always be loaded onc:mount/3, sincec:mount/3
is invoked once per LiveView life-cycle. Only the params you expect to be changed
vialive_patch/2orpush_patch/2must be loaded onc:handle_params/3.