Skip to content
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

General: Cache #448

Open
8 tasks
Oculux314 opened this issue Sep 28, 2023 · 0 comments
Open
8 tasks

General: Cache #448

Oculux314 opened this issue Sep 28, 2023 · 0 comments

Comments

@Oculux314
Copy link
Collaborator

Oculux314 commented Sep 28, 2023

Description:

We currently have data stored locally, in the store, in the cache, and on the server only.

Local storage is just in local variables in the code. The cache is global, but wiped on reload. The cache is persistent across reloads, and the server is our source of truth but expensive (and slow) to query.* Some queries are accidentally being stored in the wrong place. We should optimise this.

Acceptance Criteria:**

  • As many queries are stored locally or in the cache as possible.
  • All queries that need to be wiped on reload but still global stored in the local store.
  • Only new queries or ones that need to be up-to-date are made to the server.
  • All functionality still works.
  • Screens are automatically refreshed with the most up-to-date data upon load.

Definition of Done:

  • AC met
  • PR linked
  • Branch merged

Notes

* As far as I know. Aaron proposed this ticket - I recommend consulting with him about this ticket.
** These AC are stretch goals.

Wide-spanning ticket - communicate with #419 #447 #448 to avoid merge conflicts.

@Oculux314 Oculux314 added this to the Milestone 3: Polishing milestone Sep 28, 2023
@Oculux314 Oculux314 removed this from the Milestone 3: Polishing milestone Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant