-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDK: session expiry should be its own route #645
Comments
nikkiysendoorn1
added a commit
that referenced
this issue
Feb 19, 2024
nikkiysendoorn1
added a commit
that referenced
this issue
Feb 21, 2024
nikkiysendoorn1
added a commit
that referenced
this issue
Feb 21, 2024
nikkiysendoorn1
added a commit
that referenced
this issue
Feb 28, 2024
nikkiysendoorn1
added a commit
that referenced
this issue
Feb 28, 2024
nikkiysendoorn1
added a commit
that referenced
this issue
Feb 28, 2024
nikkiysendoorn1
added a commit
that referenced
this issue
Mar 4, 2024
nikkiysendoorn1
added a commit
that referenced
this issue
Mar 5, 2024
sergei-maertens
added a commit
that referenced
this issue
Mar 12, 2024
sergei-maertens
added a commit
that referenced
this issue
Mar 12, 2024
sergei-maertens
pushed a commit
that referenced
this issue
Mar 12, 2024
The component is responsible for cleanup of local/session storage and resetting the session expiry if not done so yet. Because the component is mounted on its own route, it will cause all other components that trigger the redirect to be unmounted and their state will automatically be reset too, leaving only the persistent storages like session/local storage to be cleaned up.
sergei-maertens
pushed a commit
that referenced
this issue
Mar 12, 2024
The expiry hook now tracks when the session will expire and performs a redirect when the session is effectively expired, which in turn triggers the necessary cleanup effects. The SessionTrackerModal is a rename of the RequireSession component, which now only has to keep track of imminent expiry of the session so that the end-user receives a warning and can opt to extend the session. Usage of these components is cleaned up, which in general simplifies state management a bit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now we have clunky state management and container routes that perform side effects (such as creating a new submission).
Instead, when the user session expires, we should (client-side) redirect to a dedicated page showing the message, and the side effect should be that any session data and state (
sessionStorage
and the like) are cleared.The text was updated successfully, but these errors were encountered: