StateTrackingManager sends phantomId as elementId

[bjork]

When adding an element in the Gantt client we get back a "real" elementId which is then added to the newly created element, the phantomId serving as a plcaeholder only. However when the state tracking manager undos a transaction, in this case removing the newly created element, it will send the phantomId as the elementId which is a little weird? Is this a bug or is there a setting somewhere that fixes this?

[saki]

I've created a ticket for our Gantt team to investigate:

https://app.assembla.com/spaces/bryntum/tickets/9351-statetrackingmanager-sends-phantomid-as-elementid/details

[bjork]

It seems like stm can handle simple additions/deletions but behaves strange when adding a task with a dependency.

To provoke this behaviour:
1) Add new successor to a task
2) Delete this successor
3) Call stm.undo()

[sergey.maltsev]

Hi, bjork!

Next time please always create new post for each separate question.

I've checked it here with your steps
https://www.bryntum.com/examples/gantt/undoredo/

First undo restores deleted successor task.
Second undo removes it.

Successor.gif (382.13 KiB) Viewed 1284 times

If you see a bug please create new post and attach code or give a detailed description what's is wrong.