5 ms·
Some pointers https://redux.js.org/recipes/implementing-undo-history https://redux.js.org/recipes/implementing-undo-history https://github.com/anthonygore/vue
by throwaway888abc 6y ago
Some pointers
https://redux.js.org/recipes/implementing-undo-history https://redux.js.org/recipes/implementing-undo-history
https://github.com/anthonygore/vuex-undo-redo https://github.com/anthonygore/vuex-undo-redo
https://medium.com/better-programming/utilizing-the-command-pattern-to-support-undo-redo-and-history-of-operations-b28fa9d58910 https://medium.com/better-programming/utilizing-the-command-...
- nadima 6y agoThanks for these resources. It looks like all of them are for frontend-only cases though?
- bradwood 6y agoOn the server-side you probably want some kind of transaction log or event sourcing / CQRS architecture... The idea being that you don't write directly to a persistence layer (database) but rather that you trigger events onto some kind of queue. These events then persist in the queue for a time and then can be asynchronously acted upon. This allows for a number of interesting patterns, including undo, replay, etc.