D&D behavior different for events dragged from partnered scheduler

[jsakalos]

The user updates the record in eventDrop event and the change is reflected when the event is dragged within the scheduler. If dragged to the partnered scheduler, the update is lost since cross-scheduler clones the event:

This only works when dragging within scheduler:

    listeners : {
        eventDrop({context}) {
            const { eventRecord } = context;
            eventRecord.name = 'hello';
        },

This works in all cases:

beforeEventDropFinalize({context}) {
    context.eventRecords[0].name = 'foo';
},

The behavior should be consistent.

Forum

[matsbryntse]

Happens since event is copied over to the new event store in the case of cross-scheduler drop. Workaround:

eventDrop({ context }) {
            console.log('eventDrop');

            const eventRecord = scheduler2.eventStore.getById(context.eventRecord.id);

            eventRecord.name += 'world';
        }

[matsbryntse]

Either remove cloning or replace data in event context after cloning in EventDrag#updateAssignments:

if (eventsToAdd) {
            context.eventRecords = eventsToAdd;
        }