[RFC] Moving to a single rehydrate action

[rt2zz]

[RFC] Moving to a single rehydrate action

[zalmoxisus]

Does it mean that the rehydration key will not match the reducer key anymore? It is not a big problem I guess, we may just catch them by payload parameters. I'd opt for less noise.

[rt2zz]

@zalmoxisus yes, there would no longer be a reducer key on the action.

By less noise, do you mean you would prefer it was consolidated to one action?

[zalmoxisus]

Yes, having a lot of reducers could generate a lot of rehydate actions in the devtool, making it difficult for debuging.

Also REHYDRATE_COMPLETE is a bit ambiguous as it is invoked only after the initial rehydratations. If we use something like persist-crosstab, one would expect to have REHYDRATE_COMPLETE when new rehydratations occur as well.

Though I agree that dealing with nested data can be error prone in custom rehydration handlers.

[rt2zz]

Will most likely make the switch in 2.0. This creates better symmetry with the getStoredState api and reduces log noise.

Will deal with the "debugability" question with a debug option.