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

react-redux-deep-reducer

v1.0.1

Published

Easily create deep parameterized reducers.

Downloads

3

Readme

react-redux-deep-reducer

Easily create deep parameterized reducers.

Installation

npm install --save react-redux-deep-reducer

Premise

Working with react/redux, things can get complicated when building applications with state dependent on configurable properties.

For example, if you're building an analytics dashboard, you may have components that display metrics based on 1) which app the user has selected and 2) a date range filter.

You might have a reducer like:

const initialState = {
  dailyViewsByAppIdAndDateKey: {
    'myApp123': {
      '2016-02-13': { /* daily views data */ },
      '2016-02-14': { /* daily views data */ },
    },
    'myApp124': { /* other app's metrics */ },
  },
};

// Even if you used `immutable` to avoid this in the reducer, you'd have something
// of similar nature in your `connect` selector function.
function reducer(state = initialState, action) {
  if (action.type === 'FETCH_DAILY_VIEWS.SUCCESS') {
    return {
      ...state,
      dailyViewsByAppIdAndDateKey: {
        ...state.dailyViewsByAppIdAndDateKey,
        [action.appId]: {
          ...state.dailyViewsByAppIdAndDateKey[action.appId],
          [action.dateKey]: {
            ...state.dailyViewsByAppIdAndDateKey[action.appId][action.dateKey],
            action.dailyViews,
          },
        },
      },
    };
  }

  return state;
}

Using react-redux-deep-reducer is similar to redux-form. You configure and use a deepReducer:

// app/reducers/index.js
import { deepReducer } from 'react-redux-deep-reducer';
import { combineReducers } from 'redux';
import dailyViewsReducer from './dailyViews';

export default combineReducers({
  // ... other top-level reducers,
  deepReducer: deepReducer({
    dailyViews: dailyViewsReducer,
  }),
});
// app/reducers/dailyViews.js
const initialState = {
  dailyViews: null,
  error: null,
};

export default function dailyViews(state = initialState, action) {
  if (action.type === 'FETCH_DAILY_VIEWS.SUCCESS') {
    return {
      ...initialState,
      dailyViews: action.dailyViews,
    };
  }

  if (action.type === 'FETCH_DAILY_VIEWS.ERROR') {
    return {
      ...state,
      error: action.error,
    };
  }

  return state;
}
// app/components/DailyViews/index.js (connected component)
import { deepConnect } from 'react-redux-deep-reducer';
import DailyViews from './component'; // "dumb" component

// based on its props, this component should use the deep state at the path [appId, dateKey]
const getInstanceKey = (ownProps) => [ownProps.appId, ownProps.dateKey];

const deepMapStateToProps = (deepState, /* topLevelState, ownProps */) => ({
  dailyViews: deepState.DailyViews,
});

const deepMapDispatchToProps = (deepDispatch, topLevelDispatch, ownProps) => ({
  fetchDailyViews: () => deepDispatch({
    type: 'FETCH_DAILY_VIEWS.BEGIN',
    appId: ownProps.appId,
    dateKey: ownProps.dateKey,
  }),
});

export default deepConnect({ domainKey: 'dailyViews', getInstanceKey },
  deepMapStateToProps,
  deepMapDispatchToProps,
)(DailyViews);