You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is a bug, a feature request, or simply a bad idea but I've noticed that the user object is stored in the Phoenix session once on login and then never updated.
I solved it for my particular case by making a refresh_user helper and calling it in the appropriate controller functions:
I reused some nice helper functions from Addict, not sure the Interactors were supposed to be used this way. Is this an approach that you'd support? Would it be useful to add this to Addict.Helper maybe? If so, I'll happily make a PR.
Or did I totally not understand something and shouldn't I be wanting to refresh the user hash in the session?
The text was updated successfully, but these errors were encountered:
Hey there!
I'm not sure if this is a bug, a feature request, or simply a bad idea but I've noticed that the user object is stored in the Phoenix session once on login and then never updated.
I solved it for my particular case by making a
refresh_user
helper and calling it in the appropriate controller functions:I reused some nice helper functions from Addict, not sure the Interactors were supposed to be used this way. Is this an approach that you'd support? Would it be useful to add this to Addict.Helper maybe? If so, I'll happily make a PR.
Or did I totally not understand something and shouldn't I be wanting to refresh the user hash in the session?
The text was updated successfully, but these errors were encountered: