Hey, we've encountered a strange problem when adding an Event in the Bryntum Scheduler.
Before describing more the issue we want to mention that we've encountered it when migrating from 3.1.3 to 4.0.3 version of the Scheduler.
We are aware of the breaking changes and we've checked the official Changelog page to mitigate the issues that can appear from migration.
The steps we are doing to reproduce the issue are:
- We go on the Scheduler and select a period by drag and drop
- Then fill all the info in the Event Editor
- Press Save
Now we get an error in the scheduler.module.js saying that "Cannot read property 'id' of undefined".
It is something strange with the following line:
const [assignmentRecord] = eventStore.assignEventToResource(eventRecord, resourceRecords);
It returns somehow 'undefined' and crashes on
DomSync.addChild(scheduler.foregroundCanvas, element, assignmentRecord.id);
We've noticed that also on v 3.1.3 it returns 'undefined' but the value was not used.