Add key argument to serialize and unserialize invocations #3
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.
Hello,
First of all, thanks for writing this library!
I came here looking for a redux-persist replacement after hitting some critical unresolved issues in my react-native apps. I'm relieved the move to redux-remember was relatively easy.
The only thing I was missing is some way to omit certain keys per reducer. I figured out I could do that by passing a custom
serialize
. But there was no way I could tell which slice I'm serializing from inside the serializer, hence this patch.Here some code that illustrates this use-case:
Just wanted to contribute back the changes I needed for my projects, hope you find it valuable.
Cheers!