Undo in Collection / Set for relation changes

[Shampra]

What’s The Bug?

Undo in collection or set doesn’t undo change in a relation value

How To Reproduce It

1. Open a collection
2. Change the title of the collection or add a relation or something else
3. Change the value of a relation ( a tag or a text in Description, what you want) and validate
4. Undo with CTRL+Z
   Your change in step 2 is undo, not the change in step 3

Image or Video

The Expected Behavior

Undo must undo the last change!

Device

PC

OS

Windows 10

Anytype Version

0.38.0

Technical Information

NA

[Angelo]

This report has been added to our issue tracker and received by the Development Team.

[crystaln]

Undo in general is unreliable, which is very concerning.

[andyotto]

Same issue here. I’m using Version 0.41.0 on MacOS.

See this screen recording: Dropbox

[jojo]

Would really need this in big sets that are sorted e.g by priority relations, if I select a relation that is the wrong priority it disappears well down into the list and i have to manually fish it out again, would just like to CMD-Z it.

[Shampra]

Globally, Undoing is not reliable, you can see it and vote here !

Undo should always works

WHAT DO YOU RECOMMEND? Undo (CTRL+Z) must always not, not sometimes only. This impacts confidence in the use of the tool and degrades the UX (because you’re implementing palliatives to this problem). HOW COULD IT BE DONE? Build an undo process that can work everywhere. ADDITIONAL CONTEXT Bugs… etc …and consequently, degraded UX (especially when compared with competing applications)

[crystaln]

As a software developer, the inconsistency of undo performance is very concerning. You can not create a reliable undo system with a patchwork of bandaids. You must use an action history system that processes all modifications, and it’s concerning that doesn’t seem to be the design of AnyType. Seems very hard to retrofit, but possible.

Undo must be reliable or one can not confidently make edits.