itsmepetrov/redux-entities

Higher-order reducer for store entities received from normalizr and makes it easy to handle them.

Redux Entities

Higher-order reducer for store entities received from normalizr and makes it easy to handle them.

Installation

npm install --save redux-entities

Usage

Use with entitiesReducer

import { combineReducers } from 'redux';
import { entitiesReducer } from 'redux-entities';
import { merge, omit } from 'lodash';

function contacts(state = {}, action) {
  const { type, payload } = action;

  switch (type) {

  case UPDATE_CONTACT:
  case REMOVE_CONTACT:
    return merge({}, state, { [payload.id]: {
      ...state[payload.id],
      isPending: true
    }});

  case UPDATE_CONTACT_SUCCESS:
    return merge({}, state, { [payload.id]: {
      ...state[payload.id],
      isPending: false
    }});

  case REMOVE_CONTACT_SUCCESS:
    return omit(state, meta.id);

  default:
    return state;
  }
}

export default combineReducers({
  contacts: entitiesReducer(contacts, 'contacts')
});

Use with combineEntitiesReducers

import { combineEntitiesReducers } from 'redux-entities';
import { contacts, groups, images, notes } from './entities';

export default combineEntitiesReducers({
  contacts,
  groups,
  images,
  notes
});

Immutable

If you want to use Immutable with Redux please check out this version of the library: redux-entities-immutable

redux-entities's Issues

Question – result & entities in state

As I understand normalizr, it always produces a structure like that:

{
  result: {
    A: [/* array of A ids */],
    B: [/* array of B ids */],
  }
  entities: {
    A: { /* A ids: values */ },
    B: { /* B ids: values */ },
  },
}

Maintaining an array of id is good for keeping the order of the different elements (and also know, the length…)
In your combine method, it seems that reducers states are only the related Entities object.

Is there a reason for that?