ReduxConnect breaks hot reloading with server side rendering

[makeomatic]

ReduxConnect breaks hot reloading with server side rendering

[hanjukim]

@michalg42 Based on my investigation, RRUHE's action handling was core cause of wrong SSR result.
https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/redux/middleware/clientMiddleware.js#L13 In here, redux-async-connect recognise promise has been finished when REQUEST promise is done, not after SUCCESS or FAILURE has been finished. Therefore, SSR result is in middle of REQUEST and SUCCESS || FAILURE. I wish my case was helpful.

[AVVS]

@michalg42 I haven't looked at https://github.com/erikras/react-redux-universal-hot-example, but as @hanjukim stated, you have to return last promise from the chain, so that you really have the complete state after all of the promises are done resolving.

Furthermore, there is 1 adjustment that had been done compared to original redux-async-connect - promises that are gathered from async components are processed sequentially, this is done to allow nested components to rely on state from parent components

If that answered your question or helped you in any way - please consider adding a note to readme,
thanks.

[AVVS]

If you have more questions - feel free to ask. Closing for now