HYDRATE and redux-dynamic-modules

Hi,

I work on a pretty complex next.js app that uses redux-dynamic-modules. Since I’ve updated next.js to 9.3 (now 9.4) I wanted to migrate from getInitialProps to getServerSideProps but I’m a bit confused about the requirement of the HYDRATE action. Does every reducer (my app has like 50+ of them) need do be able to handle that action? Is there any way to abstract it? My global redux state stores deeply nested objects so having each reducer spread through each and every field and update them with payload would be quite annoying.

Thanks.

[kirill-konshin]

Yes, you’ve pinpointed the exact reason why action constants are residing in separate files, although it’s quite tempting to put reducer, constants and action dispatchers all in one file, there are reasons not to do it.

Like I said, I am really against anything that can lead to inconsistent state, and dynamically loaded reducers is the number one reason to end up in endless debugging.

[kirill-konshin]

I’m not sure. Like I said previously, top level hydration handler is the best bet. To be completely honest, I don’t see a value to code split reducers, as it ruins the state consistency (just like in your case). Potentially actions may be handled anywhere and if the needed reducer was not loaded the action won’t be handled. Reducers are small, so what’s the point to code split them?