I am currently running into an issue with the undo implementation.
Initially this task is added.
{"type":"sync","requestId":16063416098701,"tasks":{"added":[{"parentIndex":0,"startDate":"2020-11-10T00:00:00-05:00","endDate":"2020-11-19T06:00:00-05:00","duration":9.25,"durationUnit":"day","cls":"","name":"New task 1","direction":"Forward","manuallyScheduled":false,"constraintType":null,"constraintDate":null,"percentDone":0,"effort":222,"effortUnit":"hour","effortDriven":false,"schedulingMode":"Normal","baselines":[],"parentId":28167,"type":"task","$PhantomId":"_generatedClassDefEx1"}]}}
Here is the response from the server:
{"type":"sync","requestId":16063416098701,"revision":0,"tasks":{"rows":[{"$PhantomId":"_generatedClassDefEx1","id":28169,"parentId":28167,"type":"task"}]},"success":true}
All works well until I try to undo the add. The id is still relying on the old phantomid, not the new generated id that the server responded with.
{"type":"sync","requestId":16063416162634,"revision":2,"tasks":{"removed":[{"id":"_generatedClassDefEx1"}]}}
Is this the expected behaviour?