Repository navigation
feat(cache) add caching for maps and calendars - #445
Open
mainStorne wants to merge 2 commits into
Open
mainStorne wants to merge 2 commits into
mainStorne wants to merge 2 commits into
Conversation
…t his calendar cache is deleted
This branch was successfully deployed
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.
Main Feature
Caching maps and calendars data implemented via VitePWA url patterns of routes. Then this data saved to
calendar-feedsandmapscache storage.Calendar service: NetworkFirst strategy
Maps service: CacheFirst strategy
Error requests don't use cached data only requests with connection issues will use cached data.
Invalidation strategy
When user is logout - calendar cached data is invalidated.