[Feature Request] Undo/redo: ablitity to skip adding to history and isolated undo/redo scopes/collections

[RLaipins]

Before I start I wanted to thank you for this functionality!

Is your feature request related to a problem? Please describe.
I'm running into two issues with the session undo/redo history. Maybe they are just specific to my use-case and I should try to find workarounds programmatically.

1. I can't bypass adding features to history. Currently I persist my previous drawings from localStore and load them in on page refresh with addFeatures(). Problem is that addFeatures() pushes them to the terra-draw session history. With this I can accidentally remove previously drawn features, which can be unexpected.

2. Can't isolate history between editing contexts. I have two workflows using terra-draw: regular drawing/editing, and a separate object editing mode where I programmatically load existing GeoJSON as temporary terra-draw features with addFeatures() and clean them up with removeFeatures() when editing ends. Currently if I enable session undo/redo, the second workflow messes up the history of the first and there's no way to keep them separate.

Describe your proposed idea for the solution to this problem

1. It would be nice to have a skipHistory option on addFeatures and removeFeatures so programmatically I could skip adding them to the history. Or maybe a way to clear history.

2. Named history collections and a way to switch between them. User could programmatically create additional history stores/collections and switch between them.

Describe alternatives you've considered
Manually tracking undo/redo size to allow/disallow pressing undo/redo buttons for my different workflows, but It would be flawed as I couldn't skip certain indexes or tell which history event to undo. I also contemplated creating my own undo/redo history tracker, but as there is already something inbuilt it would a shame not to use it.

[JamesLMilner]

Hey @RLaipins thanks for the issue - very much see the case where you wouldn't want to undo the initial addFeatures call. I totally appreciate your suggestions, but I think one simple way to resolve this without causing any additional complexity and adding a useful feature would be to able to wipe the history stack via the public API. This wouldn't resolve all issues, but would allow for the case where you want to avoid being able to undo the initial store restoration. I.e. here you would call addFeatures then clear the history to avoid people being able to undo it.

I'm going to keep thinking on this about now to provide more control without comprising the correctness of undo/redo stack.

[RLaipins]

Hello @JamesLMilner ! Thanks for the quick implementation. It works well for the workflow I previously described, as I can just clear history between the workflows and on initial addFeatures call. With this change, I no longer need isolated scopes or the ability to skip adding to history context. I believe this issue can be closed now. Thanks again!

[JamesLMilner]

@RLaipins no worries, there was some others messaging me on the side asking to be able to clear the history, and it also is useful for the Terra Draw website to prevent undoing the initial restoration so it made sense. I'm glad it solved your problem and we can look to closing it!