Anti-pattern: creating store in render()

[gaearon]

I've seen people do that several times. It's an easy mistake to make because <Provider>'s hot reloading capabilities also mean you can replace store at any time with a new object, and it'll transfer the state behind the scenes.

However this is wasteful performance-wise and can lead to weird issues. Can we somehow prevent people from creating the store inside render method?

[gaearon]

We can probably warn inside react-redux/Provider#componentWillReceiveProps if the store is replaced but we're in production mode.

[gaearon]

This will probably be solved by another approach to hot reloading in #350.
Closing for now.