Join egghead, unlock knowledge.

Want more egghead?

This lesson is for members. Join us? Get access to all 3,000+ tutorials + a community with expert developers around the world.

Unlock This Lesson

Already subscribed? Sign In

Autoplay

    Angular 1.x Redux: Subscribe to the Application Store

    Lukas RuebbelkeLukas Ruebbelke

    In this lesson, we are going to extend our application store with a subscribe method so that we do not have to manually query our application store every time we dispatch an action.

    In our categories controller, we are dispatching a GET_CATEGORIES action every time we want to update the categories collection within our application store. For this change to be propagated back into our controller, we need to call store.getState.

    Depending on how many times we are calling store.dispatch, this could get very cumbersome. We will extend our application by adding a subscribe method so that state changes are automatically pushed into our controller.

    angularjsAngularJS
    reduxRedux
    Code

    Code

    Become a Member to view code

    You must be a 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
    Transcript

    Transcript

    00:00 In this lesson, we are going to extend our application store with a subscribe method so that we do not have to call store.getstate every single time we dispatch an action. In our categories controller, we are dispatching a get categories action in a couple places.

    00:19 This updates the categories collection within our application store, but in order for this change to be propagated back into our controller, we need to call store.getstate. Depending on how many times we are calling store.dispatch, this could get very cumbersome.

    00:36 Let's hop into our app.store.js file, and add a subscribe method so that state change is automatically pushed into our controller. The first thing that we're going to do is create a listeners collection. We'll initialize this to an empty array.

    00:56 From here, we're going to add a subscribe method that takes a single parameter, which is listener. From here, we are going to add a listener to the listeners array. We could do this.listeners.pushlistener, but this is a mutable operation.

    01:18 In an effort to favor a mutable operations, we're going to use the spread operator to concatenate this together into a new array. From here, we're going to create an interesting function that, when it is returned, it's going to filter through the listeners collection, and return all of the listeners that do not match the listener that we passed in.

    01:52 What I've just described in an unsubscribe method. This is handy when you want to tear down a component that has a subscription. This allows us to call this method that we're returning, and then remove that from the listeners array.

    02:11 We have the ability to add listeners. We need the ability to then essentially trigger the listener that we've passed in. Generally, this is just going to be a method. When something has been dispatched, we're just going to loop through the listeners, and call the listener method.

    02:31 Let's hop into our categories controller. We are going to subscribe to our store, so this.store subscribe, and we're going to pass it in our listener method. Every time this gets called, we just want to call this.categories equals thisstore.getstate.

    02:52 We're still calling it after every dispatch. We're just abstracting out to the store. Now we can remove this line, and we can remove this line here. We're just going to keep going, and we can remove this line here. Let's hop into our browser, and see this working.

    03:12 Refresh. Let's count to about three, and let's count to three again. You can see that our categories are still updating, even though we're not manually calling the store get state within our controller. From here, let's go ahead and wire up this unsubscribe method that we're returning, just to see it working.

    03:42 This.unsubscribe equals the result of calling this.store.subscribe. We can go anywhere into this code, and call this. We'll go into our second dispatch call. We're just going to call this.unsubscribe. It's going to call it with array with two items, but then in the third call, nothing's going to happen.

    04:05 We'll refresh, count to about three, and we could count to about infinity because nothing's going to happen at this point. We have unsubscribed. This is just handy to know about so that you can wire it up, for instance, on on destroy.

    04:22 If we take it out, we'll count to three, and then we'll count to three again. Lo and behold, subscribe is working in that third dispatch block. Let's do a quick review of what we've done in this lesson. We'll go into our app store.

    04:43 You can see that we have created a listeners array that we are sending in a listener method to be added to this array. At the bottom of this, we are returning an unsubscribe method that just returns the listener from the listeners that we passed in when it's called.

    05:05 When we call dispatch, we are calling our reducer, but then we're looping through our listeners, and we're calling the listener method that we've passed in. From here, you can see that we're subscribing to the store, and passing in a method that, every time it gets called, it just calls thisstore.getstate, and returns that value, and assigns it to this.categories.

    05:31 From here, we were able to remove the explicit thisstore.getstate call after all of our dispatch calls because, implicitly, we are updating our controller every time that we call thisstore.dispatch. This is how you add a subscribe method to a store so that changes are automatically propagated to whoever is listening.

    Discuss

    Discuss