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.

Sign up for GitHub

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

Jump to bottom

Local database for caching assets #600

Closed
jaedb opened this issue Sep 3, 2020 · 1 comment
Closed

Local database for caching assets #600

jaedb opened this issue Sep 3, 2020 · 1 comment
Labels
feature request in progress

Comments

@jaedb
Copy link
Owner

jaedb commented Sep 3, 2020 •
edited
Loading

Fetching assets after every refresh of the web-app exposes the risk of overloading API quotas (as has been experienced by users). Alongside this, we need a better tool to allow the refreshing of cached/indexed data.

Moving to a local database (IndexedDB) will mean we can better store these assets with better control than Service Worker caching.

This will resolve (directly and indirectly):

It will also involve using redux-persist instead of our direct usage of localStorage.
@jaedb jaedb pinned this issue Sep 3, 2020
jaedb added a commit that referenced this issue Sep 3, 2020
@jaedb
Loading playlist library with new URI; Starting #600
6dca4ef
@jaedb
Copy link
Owner Author

jaedb commented Oct 28, 2020

Released in 3.53

@jaedb jaedb closed this as completed Oct 28, 2020
@jaedb jaedb unpinned this issue Oct 28, 2020
@jaedb jaedb mentioned this issue Nov 23, 2020
Closed
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jaedb