GithubHelp home page GithubHelp logo

arkadiuszsz / redux-thunk-subscribe Goto Github PK

View Code? Open in Web Editor NEW

This project forked from augurproject/redux-thunk-subscribe

0.0 1.0 0.0 12 KB

Makes store.subscribe available to Redux thunks

JavaScript 100.00%

redux-thunk-subscribe's Introduction

Redux Thunk Subscribe

Build Status Coverage Status npm version

Similar to Redux Thunk, but with subscribe available to thunks (in addition to dispatch and getState) so they can add listeners to the store on-the-fly.

Important note: if you just need asynchonous actions, you probably should be using Redux Thunk instead!

Usage

npm install --save redux-thunk-subscribe
var createStore = require("redux").createStore;
var thunkSubscribeEnhancer = require("redux-thunk-subscribe");

var store = createStore(reducer, thunkSubscribeEnhancer);

var thunkExclamationPoint = function () {
  return function (dispatch, getState, subscribe) {
    console.log("thunk!");
  };
};

store.dispatch(thunkExclamationPoint());

Motivation

Why make store.subscribe available to action creators (thunks)?

Redux is normally used to build UIs, which are "complete" applications in the sense that no code is expected to be supplied by the application's users. In a UI, the consumer of store.subscribe can simply be hard-coded (usually to React). Library code is different. Often, libraries expect users to supply certain pieces of code; a common example is an event handler where the user specifies a callback function. I like the Redux philosophy a lot, and in my opinion it is a good fit for library code. However, in library code, consumers of store.subscribe are not always known in advance, and, in some cases, they are intended to be defined by the library's users. This creates a problem: where does the library save the callbacks?

One option is to put the user-created callbacks in the Redux store, along with the other data. However, since the callbacks are not serializable, this breaks some nice features of Redux. Putting callbacks in the store also just feels wrong: the callbacks themselves are not really state per se, but rather observers of the state.

I think a better solution is to make store.subscribe available to action creators, so that they can set up store listeners (i.e., user-supplied callbacks) on-the-fly. That's what this library does. Since subscribe is not included in Redux's middleware API, this library is a store enhancer that changes the thunk signature from (dispatch, getState) to (dispatch, getState, subscribe).

Tests

npm test

redux-thunk-subscribe's People

Contributors

tinybike avatar

Watchers

 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.