How we learned the hard why following a flux pattern matters
summary
Shows that adopting Vuex without structure leads to real bugs like a merge checkbox sending false because components directly mutate the store and props and a mobile profile edit getting constantly overwritten by pulls. Documents a reproducible user-based action pattern inspired by Flux/Redux with request/receive/fetch namespaces, one dispatched action in the controller, and no direct mutations. Built this across 28 front-end developers, it reduces surprising state changes and makes unit tests and maintenance actually easier.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:31MULTIPLE SOURCES OF DATA
- 3:58THE MERGE REQUEST WIDGET
- 7:33YOUR ENTIRE TEAM WILL WRITE CODE THE SAME WAY
- 8:39WHAT IS FLUX?
- 9:27UNIDIRECTIONAL DATAFLOW
- 9:58NONE
- 10:16ACTION CREATORS
- 12:17ONE PATTERN, MAKING IT EASIER FOR ANYONE TO MAINTAIN THE CODE
- 13:05UNIT TESTS ARE EASIER
related talks
36mThe Flux Pattern: MVC Framework for Data
46mHow I learned to stop worrying and loved the flux
37mThe Importance of State Management in Vue
48mVueX: Vue.js applications at scale
58mFrontin' like a Back-er
26mVuex Modules in practice
31mApplying Unidirectional Data Flow Beyond the ReactJS Ecosystem
25mA cartoon guide to the wilds of data handling in React