Preserve JS Object types in state persistance #1
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.
Fantastic example repo and thanks for the write up, Instead of fighting json when hydrating the state form the store with JS types, I found since this example sticks to indexedDB that supports JS object directly, you only need to tangle with JSON if you want to use another store for compatibility like webSQL or localstorage.
It would be nice to not pull in lodash but that's a better solution that anything I tried.
1: indexedDB structured clone algorithm
2: Proxy