This repository has been archived by the owner on Feb 16, 2022. It is now read-only.
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.
What's the problem you solved?
This adds a very basic version of a storage driver that persists to IndexedDB. 5mb localstorage shackles be gone!
What solution are you recommending?
Upon the first usage of the storage, docs are hydrated into memory from a single IndexedDB row. Every time the storage upserts a doc, it writes all docs in memory back into that single row. I told you it was basic!
We do this because reading and writing stuff to IndexedDB is very slow. But this isn't an approach that'll last because of the aforementioned 'loads the whole space into memory' thing.
The storage config is stored inside of a separate object store, and works more or less as you would normally use IndexedDB.