npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

redux-chains

v1.0.2

Published

Nested reducers made easy

Downloads

6

Readme

Redux Chains

Nested reducers made easy.

This is just a small helper function that allows you to call several reducers in chain and keep the state object reference intact if the state is not modified by any of them.

Usage

In order to keep app components self-contained and nicely nested, we could use the following folder structure:

App/
|
| Sidebar/
|   |
|   | LanguageSelector/
|   |   | index.js
|   |   | actions.js
|   |   | reducers.js
|   |   | styles.css
|   |   | ...
|   |
|   | ItemList/
|   |   | index.js
|   |   | actions.js
|   |   | reducers.js
|   |   | styles.css
|   |   | ...
|   |
|   | index.js
|   | actions.js
|   | reducers.js
|   | styles.css
|   | ...
| ...

Each component contains its own set of actions and reduces the state for them.

In order to enforce a parent-child structure, parents must call their direct child reducers in order to give them the chance to reduce the state.

In this example:

App/Sidebar/actions.js

export const CLOSE_SIDEBAR = 'CLOSE_SIDEBAR';
export const OPEN_SIDEBAR = 'OPEN_SIDEBAR';

export const closeSidebar = (payload = null) => ({type: CLOSE_SIDEBAR, payload});
export const openSidebar = (payload = null) => ({type: OPEN_SIDEBAR, payload});

App/Sidebar/reducers.js

import chainReducers from "redux-chains"
import * as actions from './actions'
import itemListReducer from "./ItemList/reducers"
import languageSelectorReducer from "./LanguageSelector/reducers"

function sidebarReducer(state, action) {

    switch (action.type) {

        case actions.CLOSE_SIDEBAR:
            return {
                ...state,
                sidebarOpened: false,
            };

        case actions.OPEN_SIDEBAR:
            return {
                ...state,
                sidebarOpened: true,
            };

        default:
            return state;
    }
}

export default function reducers(state, action) {
    return chainReducers(
        sidebarReducer,
        itemListReducer,
        languageSelectorReducer,
    )(state, action);
}

In turn, each child component must call its own child reducers following the same method.