Instructor: We're using the reduced reducers library to take these individual reducers that we've created with handle action and combine them into a single reducer. This is a fairly common need.
Redux actions actually gives us a function that will take care of a lot of this wiring for us. I'm going to jump to the top of this file and I'm going to update this import to Redux actions. Instead of this singular handle action, I'm going to import the plural handle actions.
Now, I'm going to jump back down to the bottom of the file, and we're going to find that we don't need this reduce reducers call anymore once we finish this refactor, so I'll comment that out. I'm going to scroll up above these reducer definitions. I'm going to define a new constant and I'm going to call it reducer. I'm going to make this equal a call to handle actions using the ASP for plural.
Handle actions is going to take an object as its first argument. This object is a reducer map. In this reducer map is going to map action types to reducer functions.
If we look at our first individual reducer definition we have add to do, followed by a reducer function and the initial state. I'm going to take this, I'm going to copy the first two arguments, and I'm going to bring them up here and going to paste them. Instead of treating them as two arguments, I'm going to treat them as a key and value pair in this reducer map object.
I can do the same thing for each individual reducer, so I can do the same thing with loads to do's. Where loads to do's as my key and the reducer function is the value. As I do this for each one of these individual reducers, we're not going to need the reducer function anymore, so we can delete those. I'll finish this up for the rest of these reducers.
With the refactoring done, my reducer has a call to handle actions with this reducer map where each action type is a key and the reducer function for that type is the value. We have one for add to do, load to do's, update current, replaced to do, remove to do.
The last one I left out is this loader reducer that using combine actions. In order to use this, we're going to need to treat this combined action key as a computed value. Put that in square brackets, and we're going to take combined actions with our show loader and height loader and throw them in there. The same rule applies where my value is going to be my reducer function.
After the reducer map object, the second argument to handle actions is that initial state value. Now, I can get rid of this loader reducer. We can get rid of this called a reduce reducers. Now, we just need our default export to be the reducer that we've created with handle actions. I can export default reducer. We can save this and back in our browser, we can verify that our application is still working as expected.
Back in the code, if we wanted to get rid of this extra variable creation, we can take our export default. Bring it up to the top of our call to handle actions, and just do that right there. One more time, verify that we haven't broken anything.
Handle actions is going to create our individual reducers keyed off of our action type. Under the hood, it's going to do exactly what we were doing with our individual reducers using reduce reducers to create that single reducer function at the end.
Now that, we have that encapsulated in the handle actions, we can jump up to the top of the file, and we can get rid of reduce reducers, because it's being handled for us.