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
Hi! I’m using Laravel + Inertia + Vue and sharing some session-based data as global props via HandleInertiaRequests. The issue is that after I update this session data on one page and then navigate to another, the page.props does not reflect the changes unless I perform a full page refresh (F5) or call .reload() manually.
My data is purely in session, and I’d like it to stay updated across navigations without forcing a full page reload.
After session()->put('mySessionData', ...), the props do not automatically refresh in subsequent page visits.
I looked into asset versioning and tried overriding version() in HandleInertiaRequest to include a hash of the session data, which works a priori but breaks the performance of Inertia Modal for my use case and doesn’t feel like the cleanest solution.
Forcing a reload works but causes a flicker, and I’d like to avoid that.
Any advice would be greatly appreciated!
The text was updated successfully, but these errors were encountered:
Hi! I’m using Laravel + Inertia + Vue and sharing some session-based data as global props via
HandleInertiaRequests
. The issue is that after I update this session data on one page and then navigate to another, thepage.props
does not reflect the changes unless I perform a full page refresh (F5) or call.reload()
manually.My data is purely in session, and I’d like it to stay updated across navigations without forcing a full page reload.
Here’s a simplified example:
And on the frontend:
session()->put('mySessionData', ...)
, the props do not automatically refresh in subsequent page visits.version()
inHandleInertiaRequest
to include a hash of the session data, which works a priori but breaks the performance of Inertia Modal for my use case and doesn’t feel like the cleanest solution.Any advice would be greatly appreciated!
The text was updated successfully, but these errors were encountered: