Become a member
to unlock all features

Level Up!

Access all courses & lessons on egghead today and lock-in your price for life.


    Redux: Store Methods: getState(), dispatch(), and subscribe()

    0.14 - 16
    3 - 4

    We will learn about the Redux Store and demonstrate how its three methods let us implement a counter application.



    Become a Member to view code

    You must be a Pro Member to view code

    Access all courses and lessons, track your progress, gain confidence and expertise.

    Become a Member
    and unlock code for this lesson
    orLog In




    I added Redux to our application as a script act from CDNGS. This is the UMG build, so it exports a single global variable called Redux, with a capital R. In real applications, I suggest you to use NPM instead and a module bundler like webpack or Browserify, but the UMG build will suffice for our example.

    I'm going to need just a single function from Redux called create chore. I'm using ES6 destruction syntax here. It's equivalent to writing, "var creates chore equals Redux.creates chore" or, if you use NPM and something like Babel to transpile your ES6, you can write, "import creates chore," notice the parenthesis, "from Redux."

    This chore binds together the three principles of Redux. It holds the current application's state object. It lets you dispatch actions. When you create it, you need to specify the reducer that tells how state is updated with actions.

    In this example, we're calling creates chore with counter as the reducer that manages the state updates. This chore has three important methods.

    The first method of this chore is called get state. It retrieves the current state of the Redux chore. If we were on this, we're going to see zero because this is the initial state of our application.

    The second and the most commonly used chore method is called dispatch. It lets you dispatch actions to change the state of your application. If we log this chore state after dispatch, we're going to see that it has changed.

    Of course, always log into the console gets boring, so we're actually going to render something to the body with the help of the third Redux chore method, called subscribe. It lets you register a callback that the Redux chore will call any time an action has been dispatched, so that you can update the UI of your application. It will reflect the current application state.

    I'm being very naive now. I'm not using React or anything. I'm just rendering the counter into the document body. Any time the body is clicked, I'm going to dispatch an action to increment this counter.

    If you pay close attention, you will notice that the initial state, the zero, was not rendered. This is because I'm rendering inside the subscribe callback, but it doesn't actually fire the very first time.

    So I extract this logic into render method. I subscribe the render method to this chore. I also call it once to render the initial state. Now it renders the zero, and the click increments the counter. This is our first working Redux application.