[Feature]: Improve UndoManager API

Question

One thing i think would add great functionality is a more detailed history stack. U can get the undo stack and build a sort of history report from it of all the edits one has made but it is a little unclear as to what each edit was (at least to me so if I am missing something please let me know). Maybe like a formulaic description that is like component [component name] added/deleted/edited at [location on page or component added to], or component [component] text edited, . . . (please excuse t...

artf · Accepted Answer

Hi @anatoli-dp the ability to view the undo history would be actually super cool and I was already thinking about how to extend the UndoManager module in order to allow this kind of functionality via a plugin (eg. you can render the UI with your framework of choice). The UndoManager stack is updated, with a new UndoAction object (containing infos about the action), on any change of listened models/collections (components, css rules, etc.). One thing worth noting is that one change can generate...

anatoli-dp · Answer

yeah im aware of how to access the stack i just dont know how to intepret it to give a more meaningful description to the end user

artf · Answer

i just dont know how to intepret it to give a more meaningful description to the end user Each UndoAction (each instance of the stack) tells you the action type (eg. add, remove, reset, change) and details about the updated model (eg. Component, CssRule, etc.). You can try to read those data but I was thinking more about how to make each operation easily recognizable.

Improve UndoManager API

Question

Answers (4)

Related Questions and Answers

Undo manager add() not working as expected

FEAT: Mark Component as Dirty

Add a change to the undomanager

Undo manager not working properly on undoing a remove action

Paid Plugins That Match This Issue

Browse Plugin Categories