redux-funk
Declarative async outerware for Redux
What
This library enables you to declaratively specify effects in Redux reducers. You can use it to express in reducers not just what should happen, but also, what should happen next, while keeping reducers pure.
Using redux-funk, you can put all the logic and state management stuff in one place—the reducer—so you don't have to dig through multiple files to find out what happens when the UI dispatches a certain action.
This library combines (in my opinion) the best ideas from Redux Loop, redux-side-effect, and a few other libraries. It's pretty similar to Redux Loop, but the implementation is much simpler and shorter, and it enables you to program with reducers without having to worry about lifting effects.
Install
npm install redux-funk
Usage
Add declarative effects to your reducer. In this example, dispatching {type: 'INCREMENT_ASYNC'}
increments the counter after one second.
import { combineReducers } from 'redux'
import { call, coalesceFunks } from 'redux-funk'
export const incrementAsync = () => new Promise(resolve => {
setTimeout(() => resolve({type: 'INCREMENT'}), 1000)
})
const counter = (state = 0, action) => {
switch (action.type) {
case 'INCREMENT':
return state + 1
case 'INCREMENT_ASYNC':
call(action, [incrementAsync, []])
return state
default:
return state
}
}
const rootReducer = coalesceFunks(combineReducers({
counter,
funks: () => []
}))
export default rootReducer
Advantages of adding funks to the state are that you have the option to inspect them, test them, or add your own logic for handling them.
To run these funks whenever the state changes, you can use runFunks
:
import { runFunks } from 'redux-funk'
import { createStore } from 'redux'
import reducer from './reducers'
const store = createStore(
reducer
)
runFunks(store)
Here's what runFunks
does:
- Subscribe to the store. When the store updates, call each of the funks. Each funk with a return value returns a promise for an action.
- When the promises resolve, dispatch the actions.
You can use redux-funk
without runFunks
. Here are examples of why you might want to do this:
- Use callbacks instead of promises
- Only dispatch the actions after a delay
- Pass an api caller or other dependency to each funk
- etc.
Examples
See redux-funk-examples.