The work we started in this chapter is only the beginning of the refactor to Redux. I'd encourage you to continue the process in your own codebase, using the following exercises as a starting point:
- Modify the customer reducer to ensure that error is reset to false when the ADD_CUSTOMER_SUCCESSFUL action occurs.
- Update AppointmentForm to submit its data via Redux in the same way as we've done with CustomerForm. Pull out the history change from App into its own saga that is triggered when an action of type ADD_APPOINTMENT_SUCCESSFUL occurs.
- Repeat the process for CustomerSearch. This time, you can add to the existing customer reducer rather than create a new one.
- Now that you have Redux actions for CustomerSearch, remove the last of the transition logic from App and push it into a saga.