-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
Save work periodically to reduce loss from crashes #1580
Conversation
Thanks for the PR! Please comment in the issue so GitHub lets me assign it to you. Looking forward to landing this! |
Thanks, I assigned it to you. Once you've finished implementing the feature and it seems to work in a production-ready way, please mark the PR as ready for review and also ping me so I notice and come to take a look with QA testing and code review. Welcome! |
@Keavon are you d'acorde with the approach taken here? Currently this saves the document after 30 s of inactivity. Should we add a second longer timer which forces a save if no inactivity was sufficiently long? |
I was thinking that maybe a good time to save would be, if 30 seconds have elapsed, when the history stack changes. Does that seem feasible? |
887d99b
to
3f76526
Compare
8b60cbe
to
5ea0444
Compare
|
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.
Sorry this took so abnormally long to review!
Closes #929