human-redux-reactor v2.0.0

human-redux-reactor

A tool for managing your app lifecycle. React to state in your store and dispatch necessary actions.

An implementation of reactor pattern from Henrik Joreteg's book "Human Redux" <- all credit for this goes to Henrik.

Install

npm install human-redux-reactor

Setup

import { addReactorsToStore } from "human-redux-reactor";
// or
const addReactorsToStore = require('human-redux-reactor').addReactorsToStore

If you're supporting older browsers and can afford it in your bundle size budget (that's likely) you should also install a requestIdleCallback polyfill.

npm install ric

import "ric";
// or
require('ric')

If you don't do that, human-redux-reactor will still work, but run reactors in a setTimeout instead of requestIdleCallback

Use

const reactorAPI = addReactorsToStore(options)

Options:

API:

import { createReactor } from "human-redux-reactor";
import { createSelector } from "reselect";

const store = createStore(combineReducers({
    appTime: Date.now,
    // other
}))

const refresh = createSelector(
    state => (state.appTime - state.data.lastFetch > 60000),
    (timeToFetch) => {
        if (timeToFetch) {
            return fetchDataAction()
        }

    })

const reactorAPI = createReactor({
    reactors: [ refresh ],
    runIdle: true
})

reactorAPI.addToStore(store)

Infinite loop prevention

From the book:

So, as you can imagine, using this approach makes it pretty simple to create a scenario where your application is constantly reacting to the same state. Since a specific state causes these actions to be dispatched, you'll be stuck in a loop unless the dispatch immediately removes this state.

It's hard to trust yourself to never start an infinite loop, so to prevent the most obvious cases, this library has the quietPeriod option to throttle the dispatches by action type.

If an action with the same type gets returned from your reactor within a second (configurable) of the previous dispatch, it gets ignored.

If you get user interactions quicker than that, you can cancel the quiet period. Preferably by adding a reducer or hooking into interaction handling process somewhere.

You can either call cancelQuietPeriod on specific actions or use the built in reducer which cancels quiet period on every action not dispatched by a reactor.

## MIT License