Why I chose to modularize the ducks in my React App
summary
Rebuild replaces a massive index.html and a handlebars/mustache kludge with a React front end plus a Redux store that centralizes state for a Top 20 Most Binge-Worthy Shows app; actions, constants and reducers are bundled into ducks modules so one feature lives in one file; immutability bugs get fixed (use concat not push); the app aggregates data from 20+ sources, becomes maintainable, and the modularized version works and ships.
AI-written summary · about
chapters (18)
- 0:00Start
- 9:18Why React Is So Awesome
- 11:15Implementation
- 13:06Drawbacks
- 16:24What Is Redox
- 18:01The Universal Storm
- 20:14Basic Steps of Implementing Redux
- 23:44Create a Store for Wrapping Up the State
- 24:05Npm Install Redox
- 25:00Create Store
- 25:21Reducers
- 25:42What Reducers Are
- 30:14A Simple Action Creator
- 32:03Recap
- 32:20Redux Tour
- 37:52Organizing Your Redux Files
- 39:59What Are Ducks
- 47:19Resources
related talks
26mWhy I chose to modularize the ducks in my React App
26mUnleashing the Power of Duck-Typing in React: Crafting a Generic Application
25mBuilding Modular Redux Applications
29mStructure Your App's Story With Sagas and Selectors
28mBack to React: The Story of Two Apps
28mWriting better multi-process hybrid apps with React and Redux
48mGoing big with MobX
30mMake React State-Management great again