redux

Internal Refactoring & Custom Dispatchers

This release brings breaking changes necessary to start experimenting with middleware and extensibility (#6, #55). It does not bring any support for middleware per se, but it untangles “Dispatcher” (a function that tells how actions turn into state updates) from “Redux” (an instance holding the current state and managing subscriptions). It is now possible to specify your own Dispatcher if you want to experiment with ideas like middleware, time travel, action creators returning Promises or Observables, etc.

• createDispatcher now returns a function you need to give to createRedux
• createRedux is the primary API you'll use for initialization
• Instead of dispatcher prop, a dispatch function prop is injected by the <Connector> and @connect
• Instead of dispatcher prop, <Provider> and @provide accept a redux prop
• Instead of dispatcher.getAtom(), use redux.getState()
• Instead of dispatcher.setAtom(), you may pass a second initialState argument to createRedux