Adding Undo/Redo to Complex Web Apps
summary
Five minutes claims a concrete pattern: wrap every user-caused sequence in an encapsulate sequences with UUIDs identifier, persist the command and an inverse, and replay or reverse it to implement undo redo even when side effects and backend ops run concurrently. Example: a todo flow produces several triggered actions but bundling them under one id lets the system move cleanly between states. The talk points to an article on the content Square engineering blog and outlines map each action to its opposite as the core rule.
AI-written summary · about
chapters (5)
- 0:00Introduction to undo redo
- 0:31Basic state management
- 1:25Addressing complex state
- 2:46Implementing the solution
- 4:12Conclusion and resources
related talks
32mCRDT and other new ideas for client-server communication
13mHow we learned the hard why following a flux pattern matters
36mThe Flux Pattern: MVC Framework for Data
29mReduced Redux
31mReplicated Redux
57mFirst Class Commands: The 2017 Edition
57mUnlocking The Awesome Power of Refactoring
21mAsynchronous UX