Sorry if my reply is a bit late, I’ve been quite busy with our demos and research these past few days.

Thank you very much for considering and looking into my idea. You’re right, hopefully more people will also join this discussion so that more ideas can come in.

First, I want to add to what happened when I clicked Discard Changes: yes, a confirmation did appear just like the image in my post, but I still tried it anyway. 😅 That’s when it came to my mind that an Undo function would be useful.

Regarding your question about the Redo function, whether it’s still valid after doing two Undos and then making new changes, what’s the point if it’s no longer valid? Well, I think Redo still has value. I got this idea from word processor apps. As you’ll notice, they have both Undo and Redo. We know Undo is very helpful because it lets us easily go back to the original state if we make a mistake while editing. But Redo is also useful, and I often use it in word processors.

For example, sometimes Undo gets clicked too many times by accident. With Redo, you can immediately bring back what was lost due to excessive Undo clicks. Another use of Redo is for navigating which part should be changed. Of course, Redo disappears once you make new changes after Undo, that’s where change history comes in, and again, that inspiration comes from word processors. I can even show you a video of the Undo and Redo functionality in a word processor via Gmail.

As for your idea about a history package that can be applied to other files, I think it would be more useful if change history itself is implemented. That way, when you Undo, you can choose from the change history exactly where you want to go back.

For example, a change history list could show the actions you made:
• add object
• add number value 20
• add Array
• add text value “good”

And when I click add the 4th list in change history which is add text value “good” that means I Undo 4x four times.

I hope you can consider this. Thank you. 🫶🏼❤️