If I understand correctly, I can prevent a change from being undone by setting the meta addToHistory as false. It is done by analysing each transaction and setting the plugin state accordingly in the apply. However, if other plugins append a transaction in appendTransaction and do not set the addToHistory meta, the addToHistory in the plugin state will be reset. Is this the desired behaviour?
Sorry, I forgot to specify this is related to y-prosemirror.
Well, one could argue both ways whether to include it all the transactions or just the original one. If I were you, I’d just deal with it and set the meta field in the appended transactions as well. It’s always non-optimal to modify the API after people have accommodated to its current behavior.