Skip to content

feat(cache) add caching for maps and calendars - #445

Open
mainStorne wants to merge 2 commits into
mainfrom
maps-calendar-caching
Open

mainStorne wants to merge 2 commits into
mainfrom
maps-calendar-caching

Conversation

@mainStorne

@mainStorne mainStorne commented Sep 23, 2026 •

Copy link
Copy Markdown
Member

Main Feature

Caching maps and calendars data implemented via VitePWA url patterns of routes. Then this data saved to calendar-feeds and maps cache storage.

Calendar service: NetworkFirst strategy

  • Requests recourse and if it available it will use it.
  • Otherwise if recourse is unavailable due of connection issues then it will be received from cache.

Maps service: CacheFirst strategy

  • Recourse will be get from cache.
  • Otherwise resource is requested.
    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.

@github-project-automation github-project-automation Bot moved this to 📋 Backlog in InNoHassle Sep 23, 2026
@mainStorne mainStorne moved this from 📋 Backlog to 🏗 In progress in InNoHassle Sep 23, 2026

This branch was successfully deployed

1 active deployment
pre — 6c80e184 Deployed Sep 23, 2026 by mainStorne via Build static files #1409
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🏗 In progress

Development

Successfully merging this pull request may close these issues.

1 participant