Why I chose to modularize the ducks in my React App
summary
Claims that bundling Redux pieces into ducks (action types actions reducers in one file) reduces boilerplate and makes feature work discoverable. Uses React and Redux with createStore reducers and action creators to add an AddShow flow to a most binged TV show app, moving constants actions and reducer into a single module. Notes that 95% of cases need one reducer/action pair and that the AddShow feature fits in 21 lines of code and runs unchanged.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:43Modularized and Reusable Components
- 3:07Reusability
- 7:04Redux
- 7:48The Global Store
- 9:22Create a Store
- 10:25What Reducers Do
- 11:08Creating a Reducer
- 14:52Recap the Main Redux Concepts
- 17:31Way of Organizing Your Redux Files
- 19:29What Are Ducks
- 20:44Convert Our Redox to Ducks
- 22:01Actions
- 22:30Merge In and Handle the Reducer
- 25:42Conclusion
related talks
48mWhy I chose to modularize the ducks in my React App
51mBuilding React Applications with Redux
25mBuilding Modular Redux Applications
28mWriting better multi-process hybrid apps with React and Redux
15mStop using Redux
44mThe Fundamentals of Redux
26mUnleashing the Power of Duck-Typing in React: Crafting a Generic Application
05mReducing Redux Boilerplate