Redux-persist with combined reducers about ignite-andross HOT 9 CLOSED

Our transform for redux config needs to be brought up to date. This is from the ReduxPersist 2 days.

from ignite-andross.

@skellock - Do you think we should be using https://github.com/rt2zz/redux-persist-immutable ???

@vincejah - can you give this a go and let us know if it works? https://github.com/rt2zz/redux-persist-transform-immutable

from ignite-andross.

That one is for Immutable.js I think. But ya, we’d need the seamless-immutable version of that.

from ignite-andross.

i get this without an second combineReducers too

from ignite-andross.

This seems related to this issue and it appears this line that is causing it. As @skellock speculated, this seems unnecessary as of this merge request. Commenting out L29 in ImmutablePersistenceTransform seems to resolve the issue.

UPDATE: made a pull request to remove the line

from ignite-andross.

Thx @heyjared !

from ignite-andross.

How do i persist specific properties of the reducer? For example I have a login reducer which has properties such as username, password, employee_number. In this case I want to persist just the employee_number and not the username and password. Is this possible? If yes then can you please post an example?

from ignite-andross.

If you only want to persist certain parts I suggest 2 methods.

1 - Move just those parts to a separate reducer that is rehydrated.
2 - Store them yourself with Async storage
^ plenty of examples of that in the docs, and it comes free with RN

from ignite-andross.

@GantMan Redux persist gives the ability to blacklist nested state properties
When this is implemented, it breaks the app

from ignite-andross.