Add Storage API persistence to protect calendar data - #12
Open
prybalko wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Storage API persistence to protect calendar data
Summary
Requests persistent storage using navigator.storage.persist() to reduce the risk of browsers automatically clearing user calendar data.
Changes
useEffecthook inCalendarContext.tsxto request persistent storage on app loadBenefits
Notes
Browsers typically grant persistence based on user engagement (bookmarking, frequent visits, PWA installation). The app continues to work normally whether persistence is granted or denied.