Find a way to cut getReducer and replaceReducer from the API

[gaearon]

They are used for hot reloading by react-redux and code splitting. However the solution feels wrong and ad-hoc to me.

Something like a store enhancer that would wrap the reducer a la devTools seems like the way forward. This way hot reloading would be opt in, but much more reliable.

Whatever the solution may be, it has to solve the following issues to be considered:
#37 #301 #340 #346 #348 reduxjs/redux-devtools#68

Ideas welcome!

[taylorhakes]

Here is my proposal. I am sure it has some issues.

Expose reducer as a simple function to Higher Order Stores.

Higher order stores would be created like this:

createStore(middleware, devtools, persistState);

Higher Order Stores would have the following signature:

function higherOrderStore({ reducer, dispatch, getState, subscribe }) {
  // wrap components

  return {
    reducer: newReducer,
    dispatch: newDispatch,
    // ...
  };
}

The create store function would have the following signature

createStore(...funcs) {
  const store = new Store();
  const finalStore = compose(...funcs, store);
  finalStore.dispatch({ action: '@@init' });
  return store;
}

This allows the store to be very flexible. @@init can be called by other components or not at all.

This is just off the top of my head. Haven't thought of all the implications of this change. It definitely would solve #376 though.

[gaearon]

Interesting, thanks. On the first sight I like it, but I haven't thought through the implications.
I'd say we'll release 1.0 as is, but this will be on our radar as the next important breaking change.