sequential redux action s
Table of Contents
An alternative approach to redux where we put actions first, and view state as a consequence of them.
Instead of creating singleton reducers responsible for a single state slice, we create reducers for each individual action that can act across the entire state.
Should an action have consequences, they are declared on the action itself (as an event-emitter).
$ npm i -S conduxion
Please note that
redux is a peer-dependency.
Creating a store
Using pre-fab factories.
;;? action.reducerstate, action.payload: state;;;
For your convenience, we also expose a dev version that automatically connects to Redux DevTools
;;? action.reducerstate, action.payload: state;;;;
Creating an action
Using the actionCreatorFactory() factory function.
Creates a conduxion redux store with consequence middleware applied.
Creates a conduxion redux store with consequence middleware as well as Redux DevTools middleware applied.
Redux root reducer for conduxion.
The base interface for all conduxion actions. Enables use of consequence methods.
An action consequence method.
Generic representation of a conduxion action.