Copying events between schedulers is not correct

[pmiklashevych]

Forum: https://www.bryntum.com/forum/viewtopic.php?p=80095#p80095

http://lh/bryntum-suite/scheduler/examples/drag-between-schedulers/
When events in both schedulers have the same IDs, and you copy such events to another scheduler, it disappears.
See updateRecords and updateAssignments functions in EventDrag class. They have to be refactored.

Testcase1:
Set the first task id in Scheduler1 to existing id in Scheduler2:

    events    = [
        {
            id           : 11, // was 1 before
            resourceId   : 1,
            name         : 'First Task',

Drag "First task" from Scheduler1 to Scheduler2. See the task element disappears. Depends on the resource and time where you drop the result might be different, but it always buggy this or that way.

Testcase2:
There is copyKeyPressed hardcoded to false in updateRecords function. Try to set it to true.
Reload the page. Drag "First task" with Id 11 to the Scheduler2. It works. Drag another task from Scheduler1 to Scheduler2.
See the error:

SharedEventStoreMixin.js:388 Uncaught (in promise) TypeError: Cannot read property 'meta' of null
    at EventStore.update (SharedEventStoreMixin.js:388)
    at AssignmentStore.trigger (Events.js:1102)
    at AssignmentStore.dataReady (AbstractPartOfProjectStoreMixin.js:39)
    at ProjectModel.trigger (Events.js:1102)
    at ProjectModel.doCommitAsync (SchedulerCoreProjectMixin.js:384)
    at async Promise.all (/bryntum-suite/scheduler/examples/drag-between-schedulers/index 0)
    at async EventDrag.updateAssignments (EventDrag.js:621)
    at async EventDrag.updateRecords (EventDrag.js:381)
    at async EventDrag.finalize (DragBase.js:520)

[JockeLindberg]

This is related to the EventDrag feature.