No I never pursued a solution. I’m pretty sure what I suggested above is possible but I’m not really sure it’s best practice.
tfwright
mindok
Ok, thanks. I know who my users are so I’ll just write a home-made user state store with updates straight from the liveviews.
0
shahryarjb
i’m confused, we put session with normal redirect to live router? and add session on live router ? that’s it? like
live "/foo", FooLiveView, session: [:user_id]
it’s oky, but how can update phoenix session in phoenix liveview, becuase I used Oauth2 protocol, and every request I have to send refresh_token and access_token, and update new refresh_token after this. but I’m using Liveview, how can I do? I just can create a normal router which is AuthController but all of my pages are Phoenix liveview
and I have one more question, we have to pass new token every page ? in Liveview ? what about after updating session ?
1
toranb
I realize I’m really /really/ late to the party but I did blog up a solution I put together for login & signup forms in Phoenix LiveView if anyone is still hunting around for options
8
henrik
And I’ve blogged about storing data in the session in LiveView: Persistent session data in Phoenix LiveView – The Pug Automatic
5
ricardo-h
It seems that there is still no consensus pattern to solve the state management with liveview.
1
kuon
My solution was to create the login form in a live view, and when the login succeed, I generate a phoenix token and I redirect to /login/:token with a redirect in the live view, /login/:token is a normal controller that check the token and use put_session on the conn as usual.
1
slashmili
TL;DR: use phx_trigger_action
I’ve came across this thread multiple times past few months while I was looking for a solution, I was about to implement the workaround that people are offering(calling an API to set session) here but I learned about phx_trigger_action attributes for form bindings.
The
phx-trigger-actionattribute can be added to a form to trigger a standard form submit on DOM patch to the URL specified in the form’s standardactionattribute. This is useful to perform pre-final validation of a LiveView form submit before posting to a controller route for operations that require Plug session mutation.
Kudo goes to Pragmatic Studio’s Phoenix LiveView couse. I highly recommend it!
13
shahryarjb
when you use this you have this problem Bug in navigating from a controller to a LiveView page (put_flash message will not be deleted)
0
daveboo
This seems too good/simple to be true…did you have any trouble down the road using this approach?
0