Redux-Tiles

Documentation

Redux is an awesome library to keep state management sane on scale. The problem, though, is that it is toooo verbose, and often you'd feel like you are doing literally the same thing again and again. This library tries to provide minimal abstraction on top of Redux, to allow easy composability, easy async requests, and sane testability. It is possible to start using this library in existing project, adding new functionality gradually.

More about rationale behind this library

Features: - built-in async handling - nesting (no several levels merging of state) - caching (call your requests declaratively, while only one will be fired) - semantic separation of reducers (no manual combineReducers)

You can see comparison between redux-tiles and vanilla redux

Examples * Calculator * TodoMVC * Hacker News API * Github API

Installation

To install latest stable version, run:

npm install --save redux-tiles

This package was built with the idea in mind, that people will use it usually using some bundling tool – Webpack, Browserify or Rollup. The package itself is written in TypeScript, and therefore provides typings out of the box.

If you for some reason don't use bundler, you can use UMD builds, which are located in dist folder. Just include it in your page via script tag, and then you will have it under window.ReduxTiles global variable.

TOC:

• Example of use
• Rationale
• Integration API
• Tiles API
• Nesting
• Middleware
• Server-side Rendering
• Selectors
• Tests

Example of use

More comprehensive example

import { createTile, createSyncTile } from 'redux-tiles';

// sync tile to store information without any async stuff
const loginStatus = createSyncTile({
  type: ['user', 'loginStatus'],
  fn: ({ params: status }) => ({
    status,
    timestamp: Date.now(),
  }),
});

// request to the server
// it is absolutely separated, so it is very easy
// to compose different requests
const authRequest = createTile({
  type: ['user', 'authRequest'],
  // we have access to dispatch, actions, selectors, etc –
  // we can pass all what we need when creating middleware
  // it allows us to test easier, and also compose other tiles
  fn: ({ params, api, dispatch, actions, getState }) =>
    api.post('/login', params),
});

// actual business logic
// note that we don't use direct `api` calls here
// we just compose other basic tiles
const authUser = createTile({
  type: ['user', 'auth'],
  fn: async ({ params, dispatch, actions, selectors, getState }) => {
    // login user
    const { data: { id }, error } = await dispatch(actions.tiles.user.authRequest(params));

    if (error) {
      throw new Error(error);
    }

    // set up synchronously user status
    dispatch(actions.tiles.user.loginStatus(true));

    return true;
  },
});

Rationale

There are enough projects around to keep your state management clean (for example), but they are mostly about organizing, rather than removing burden of repetitive stuff from the developer. Other packages offer you full-fledge integration with REST-API, normalizing your entities, building relations between models, etc. There is nothing like this here – in fact, if you need something like this, with the ability to query your local "database", I highly advise you to create your own solution, which will be custom-tailored to your specific problem.

This package focuses on very basic blocks, which are good for pretty simple applications (e.g. login/logout, fetch client data, set up calculator values).

Integration API

Despite being easy-to-use package to write new modules, you'd have to do some work to integrate it into your project. In a nutshell, you have to have a middleware which will handle returned functions from dispatched actions (one is provided in this package, but redux-thunk will suffice as well), and then you have to combine all modules to create actions & reducers. It is better to see in a small example:

import { createTile, createEntities, createMiddleware } from 'redux-tiles';
import { createStore, applyMiddleware } from 'redux';

const clientDataTile = createTile({
  type: ['client', 'data'],
  fn: ({ api, params}) => api.get('/client/info'),
});

const tiles = [
  clientDataTile,
];

const { actions, reducer, selectors } = createEntities(tiles);

// we inject `actions` and `selectors` into middleware, so they
// will be available inside `fn` function of all tiles
const { middleware } = createMiddleware({ actions, selectors });

createStore(reducer, applyMiddleware(middleware));

Tiles API

Tiles are the heart of this library. They are intended to be very easy to use, compose and to test. There are two types of tiles – asynchronous and synchronous. Modern applications are very dynamic, so async ones will be likely used more often. Also, don't constrain yourself into the mindset that async tiles are only for API communication – it might be anything, which involves some asynchronous interaction (as well as composing other tiles) – for instance, long polling implementation.

Full documentation for async tiles

import { createTile } from 'redux-tiles';

const photos = createTile({
  // they will be structured api.photos inside redux state,
  // and also available under actions and selectors as:
  // actions.tiles.api.photos
  type: ['api', 'photos'],


  // params is an object with which we dispatch the action
  // you can pass only one parameter, so keep it as an object
  // with different properties
  //
  // all other properties are from your middleware
  // fn expects promise out of this function
  fn: ({ params, api }) => api.get('/photos', params),


  // to nest data:
  // { 5:
  //    10: {
  //      isPending: true,
  //      fetched: false,
  //      data: null,
  //      error: null,
  //   },
  // },
  // if you save under the same nesting array, data will be replaced
  // other branches will be merged
  nesting: (params) => [params.page, params.count],


  // unless we will invoke with second parameter object with asyncForce: true,
  // it won't be requested again
  // dispatch(actions.tiles.api.photos(params, { asyncForce: true }))
  caching: true,
});

We also sometimes want to keep some sync info (e.g. list of notifications), or we want to store some numbers for calculator, or active filters (todoMVC is a good example of a lot of synchronous operations). In this situation we will use createSyncTile, which has no meta data like isPending, error or fetched, but keeps all returned data from a function directly in state.

Full documentation for sync tiles

import { createSyncTile } from 'redux-tiles';

const notifications = createSyncTile({
  type: ['notifications'],


  // all parameters are the same as in async tile
  fn: ({ params, dispatch, actions }) => {
    // we can dispatch async actions – but we can't wait
    // for it inside sync tiles
    dispatch(actions.tiles.user.dismissTerms());

    return {
      type: params.type,
      data: processData(params.data),
    };
  },

  // alternatively, if you perform some actions on existing data,
  // it might be useful to write more declarative actions
  // they have exactly the same signature and dispatch returned data
  // to the tile
  fns: {
    add: ({ params, getData, selectors, getState }) => {
      // same as:
      // const currentData = selectors.notifications(getState(), params);
      const currentData = getData();

      return {
        ...currentData,
        data: currentData.concat(params.data),
      };
    },
  },

  // you can pass initial state to sync tile
  // please, be careful with it! if you use nesting, then
  // you have to specify nested items (otherwise selectors will
  // return undefined for your nested item)
  initialState: {
    terms: {
      type: 'terms',
      data: []
    },
  },

  // nesting works the same way
  nesting: ({ type }) => [type],
});

Nesting

Full documentation on nesting

Very often we have to separate some info, and with canonical redux we have to write something like this:

case ACTION.SOME_CONSTANT:
  return {
    ...state,
    [action.payload.id]: {
      [action.payload.quantity]: {
        ...state[action.payload.id],
        ...action.payload.data,
      },
    },
  };

Or with Object.assign, which will make it even less readable. This is a pretty common pattern, and also pretty error prone – so we have to cover such code with unit-tests, while in reality they don't do a lot of intrinsic logic – just merge. Of course, we can use something like lodash.merge, but it is not always suitable. In tiles we have nesting property, in which you can specify a function from which you can return an array of nested values. The same code as above:

const infoTile = createTile({
  type: ['info', 'storage'],

  // params here and in nesting are the same object
  fn: ({ params: { quantity, id }, api }) => api.get('/storage', { quantity, id }),

  // in the state they will be kept with the following structure:
  // {
  //   someId: {
  //     5: {
  //       isPending: true,
  //       fetched: false,
  //       data: null,
  //       error: null,
  //     },
  //   },
  // }
  nesting: ({ quantity, id }) => [id, quantity],
});

Middleware

In order to use this library, you have to apply middleware, which will handle functions returned from dispatched actions. Very basic one is provided by this package:

Full documentation for middleware

import { createMiddleware } from 'redux-tiles';

// these are not required, but adding them allows you
// to do Dependency Injection pattern, so it is easier to test
import actions from '../actions';
import selectors from '../selectors';

// it is a good idea to put API layer inside middleware, so
// you can easily separate client and server, for instance
import api from '../utils/api';


// this object is optional. every property will be available inside
// `fn` of all tiles
// also, `waitTiles` is helpful for server-side-rendering
const { middleware, waitTiles } = createMiddleware({ actions, selectors, api });
applyMiddleware(middleware);

Also, redux-thunk is supported, and in order to pass your own properties you should inject this object to redux-thunk. Also, there is nothing bad to just import actions and selectors on top of the files, but then testing might require much more mocking, which can make your tests more brittle.

Server-side Rendering

Article about SSR with prefetch

Redux-tiles support requests on the server side. In order to do that correctly, you are supposed to create actions for each request in Node.js. Redux-Tiles has caching for async requests (and keeps them inside middleware, so they are not shared between different user requests) – it keeps list of all active promises, so you might accidentaly share this part of the memory with other users!

Also, to make this part of functionality working, you have to use redux-tiles middleware, or pass promisesStorage object to redux-thunk additional object (more in caching section in docs).

```javascript import { createMiddleware, createEntities } from 'redux-tiles'; import { createStore, applyMiddleware } from 'redux'; import tiles from '../../common/tiles';

const { actions, reducer, selectors } = createEntities(tiles); const { middleware, waitTiles } = createMiddleware({ actions, selectors }); const store = createStore(reducer, {}, applyMiddleware(middleware));

// this is a futile render. It is needed only to kickstart requests // unfortunately, there is no way to avoid it renderApplication(req);

// wait for all requests which were fired during the render await waitTiles();

// this time you can safely render your application – all requests // which were in componentWillMount will be fullfilled // remember, `compone