No-op sub state change prevents auto rehydration about redux-persist HOT 7 CLOSED

@IanVS yes that matters, autoRehydrate only looks at the first level of state. So in this case you have a few options:

1. dont use autoRehydrate and have all of your reducers implement REHYDRATE
2. have none of your sub reducer handle REHYDRATE (then autorehydrate will work as expected)
3. write a custom version of autoRehydrate that does exactly what you need.

from redux-persist.

This is by design, autorehydrate checks for object equality.

Do you have a reducer that makes this behaivor problematic?

from redux-persist.

I was able to fix my reducers that were causing the problem, but I filed
this in case it was unintended. Since it's by design, feel free to close it.

On Sat, 31 Oct 2015 at 14:38 Zack [email protected] wrote:

This is by design, autorehydrate checks for object equality.

Do you have a reducer that makes this behaivor problematic?

—
Reply to this email directly or view it on GitHub
#34 (comment).

from redux-persist.

I will leave this open for a bit to see if anyone else wants to weigh in.

The rationalization is, if the reducer handles the the REHYDRATE action, it implies custom rehydration and based on this assumption autoRehydrate will skip that reducer. This also is nice because it prevents conflicts where autoRehydrate might overwrite something the reducer wanted.

from redux-persist.

Sounds reasonable to me.

On Tue, 3 Nov 2015 at 12:34 Zack [email protected] wrote:

I will leave this open for a bit to see if anyone else wants to weigh in.

The rationalization is, if the reducer handles the the REHYDRATE action,
it implies custom rehydration and based on this assumption autoRehydrate
will skip that reducer. This also is nice because it prevents conflicts
where autoRehydrate might overwrite something the reducer wanted.

—
Reply to this email directly or view it on GitHub
#34 (comment).

from redux-persist.

If a nested reducer handles the REHYDRATE action, is that entire reducer skipped? For example:

function subReducer1(state = initialState, action) {
  switch (action.type) {
  case 'ITEMS_UPDATED':
    return {...state, items: actions.payload};  
  default:
    return state;
}

function subReducer2(state = initialState, action) {
  switch (action.type) {
  case REHYDRATE:
    return {...state};  // presumably something more complicated here
  default:
    return state;
}

const topReducer = combineReducers({
    subReducer1,
    subReducer2,
});

In the above example, will subReducer1 still be auto-rehydrated? In my testing so far, it does not seem to be.

from redux-persist.

Actually, in my case I have one more level of combineReducers, so it's more like:

const topReducer = combineReducers({
    anotherReducer,
    midReducer: combineReducers({
        subReducer1,
        subReducer2,
    });
});

Not sure if that makes any difference.

from redux-persist.