Code 401: Class 38 - Redux Asynchronous Actions

---

Questions

1. How granular should your reducers be? In most cases it will probably be beneficial to have a unique reducer for each action so that it be reused in other processes

2. Pro or Con – multiple reducers can “fire” when a commonly named action is dispatched In most cases this is probably a con because it would be difficult to make independent changes if necessary

3. Name a strategy for preventing the above Separate out the actions so each calls a specific reducer

Vocabulary

• Store the top level storage of all state in Redux
• Combined Reducers a single reducer that takes in two or more other reducers and returns a single function

Watch: Dan Abramov on Suspense

• Video Unavailable

Read: Async Actions

• Redux middleware enables writing logic with side effects
• Redux Thunk middleware allows us to write functions that get dispatch and getState as arguments
• $npm install redux-thunk
• import thunkMiddleware from 'redux-thunk'
• const composedEnhancer = composeWithDevTools(applyMiddleware(thunkMiddleware))

Read: Thunk Middleware

• Allows you to write action creators that return a function instead of an action
• Can be used to delay dispatch or conditionally dispatch
• “The term originated as a humorous past-tense version of ‘think’.”
• import { createStore, applyMiddleware } from 'redux';

Read: Redux Thunk

• Redux is synchronous by default
• Redux-Thunk is only 14 lines of code!

---

Return to reading-notes Deployed Site

Return to reading-notes Mark Down