We've found a weird bug. Creating a task in SchedulerPro, and afterwards just checking if a dependecy is valid through dragging dependency, undoing the task and redoing it, breaks the scheduler. See attached video.
We've found out that it also breaks undo/redo tasks created after the dependency check. Meaning that if our users want to create dependencies by dragging we will have to completely disable STM else our users might break their schedule afterwards. It is not enough to reset the queue.
Is there a work around? The best I have found is overwriting validateDependency or isDependencyCyclic functions, but then we can't use the option to validate. It is hard for me to see if this creates problems elsewhere in the code.
Thanks for letting us know, I added a note to the ticket. For now, no work arounds besides the one that you did, but we already have our team working on the ticket and trying to fix it as quickly as possible.
Hi Andreas. I'm trying to reproduce this exception using our latest online examples and its not reproducible. Attaching a video in the github ticket: https://github.com/bryntum/support/issues/6209. Hopefully it has been fixed along the way from 5.2.10 to 5.3.2.
Please try with the latest code on your end and if its still reproducible provide some additional info?