[SuperEditor] Support undo/redo

[matthew-carroll]

Refactor all existing DocumentEditor behaviors to support undo/redo, probably by way of an event-source solution.

[ChenHaoTech]

It's October 2023 now. why hasn't it been changed? how can I support undo redo? 😢

[WillianSalceda]

Any updates?

[matthew-carroll]

We've migrated to atomic commands, which was a critical pre-requisite for undo/redo. We're still vetting that system, which is comprised of requests, commands, and reactions.

We haven't started working directly on undo/redo yet.

[alterhuman]

@matthew-carroll @angelosilvestre any plans on this? This is a pretty important feature for any editor.

[matthew-carroll]

This is being developed right now

[simonbengtsson]

This would be awesome! My use case for this is native fidelity. Undo/redo with cmd + z and cmd + shift + z is the only thing I'm personally experiencing as being different when writing on desktop in super editor compared to Flutter's text field or native text fields on macOS such as those in Safari or Apple Notes etc. When writing on macOS I'm often using undo/redo to undo/redo a deletion or undo/redo pasted content etc.

The editor I'm working on is light and have no immediate requirements for custom components etc. The main reason I want to use a third party editor such as super editor compared to Flutter's text field is the the support for ordered and unordered lists in addition to the easier way to add support for styling such as bold and code formatted text.

[matthew-carroll]

@simonbengtsson can you clarify whether you're asking for this in SuperEditor or SuperTextField? One is a document editor, the other is a text field.

[simonbengtsson]

Right! I should have posted this in #189 if I had found this before posting since my use case is actually a text field I believe. It is applicable to both however ie the undo/redo use case as described above is the same for both document editors such as the one in Google Docs and text fields such as the one here on Github where I'm writing this comment.

[hannutho]

Hey! How is development going on this? When is a initial version expected to be released?

[matthew-carroll]

@hannutho please see #1900 for the status of the work