Uploaded June 2016 | Updated September 2026, 1 week ago
Async Actions with Redux are a piece of cake...you just have to know what to do. Handling Ajax in Redux is as simple as firing off several actions: one for start, one for completion, one for error.
Dispatching multiple, synchronous actions allows your React layer to still be a 100% static representation of the state of your store. So React itself will never have any application state, only your store will. This is the biggest hangup of developing React/Redux applications - where do you keep state? Once you learn that 100% of the application state lives in the store, everything gets drastically simpler in Redux.
-~-~~-~~~-~~-~-
Also watch: "Tailwind CSS - why CSS utility classes save so much time"
youtube.com/watch?v=oU5ar0dmQEY
-~-~~-~~~-~~-~-
Async Actions with Redux are a piece of cake...you just have to know what to do. Handling Ajax in Redux is as simple as firing off several actions: one for start, one for completion, one for error.
Dispatching multiple, synchronous actions allows your React layer to still be a 100% static representation of the state of your store. So React itself will never have any application state, only your store will. This is the biggest hangup of developing React/Redux applications - where do you keep state? Once you learn that 100% of the application state lives in the store, everything gets drastically simpler in Redux.
-~-~~-~~~-~~-~-
Also watch: "Tailwind CSS - why CSS utility classes save so much time"
youtube.com/watch?v=oU5ar0dmQEY
-~-~~-~~~-~~-~-










