(docs): note redux-persist's Storage Engines compatibility #78
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- redux-persist's Storage Engines all follow the same localForage-style
async Promise API, so they should all be compatible with mobx-persist
as well
- docs should mention this as the interoperability adds many more
usage options for developers
- e.g. using node-storage or cookie-storage for Node or universal
apps
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
async Promise API, so they should all be compatible with mobx-persist
as well
usage options for developers
apps
Ripped out of agilgur5/mst-persist#15 as discovered in agilgur5/mst-persist#13
First commit back / collaboration since I created
mst-persistfrom #37! :)