How to Redux

How to Redux

When I see the way that people are using Redux in real apps, it occurs to me that a lot of people are adding complications to their apps, and not reaping the true benefits of Redux. To find out if you’re reaping the true benefits of Redux and the Flux architecture, honestly answer these questions:

  1. Are my components/views making network requests or maintaining app state?
  2. Are my reducers mutating shared state? See “What is a Pure Function?”
  3. Do I need to mock things to test my components, async actions, or reducers?

If the answer to any of these questions is “yes” or “I don’t know”, it’s time for a refresher on Flux and Redux architecture. Why we are interested in them in the first place, and how can they make your apps easier to manage?

Assignments

  1. Read “The Best Way to Learn to Code is to Code: Learn App Architecture by Building Apps”
  2. Clone the project and build unit tests and reducers for the “Rejection” app
  3. Ask another student in the “Learn JavaScript Chat” to review your code on GitHub.

Links