-
Notifications
You must be signed in to change notification settings - Fork 4
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
document session management strategy #364
document session management strategy #364
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I notice there's a question mark here:
When the FE timer reaches 20 minutes (?) ...
Do we need input from design or someone else to confirm 20 minutes as a reasonable starting point? Seems like a reasonable starting point to me, and easy enough to adjust if needed.
Yes. I'll remove the question mark, but we can adjust if necessary.
|
removed question mark
Sorry, my sentence could have used an editor or two. I mean that the AC for 282 says that tasks are documented inside 197. Merging this PR will automatically close 282, so I want to be sure we don't forget to actually write out the tasks inside 197 before that happens. |
Sorry about that. I misunderstood what you were saying. 197 is now tasked out.
|
…t-tech/TANF-app into documentation/282/session-management � Conflicts: � tdrs-backend/docs/session-management.md
For some reason, `throttle` in `react-idle-timer` package was not working correctly when trying to dispatch an action. `Debounce` does work as expected.
Added where timeout is set and removed a question mark
This pull request changes...