Having upgraded to bryntum/scheduler@5.2.3 and Angular 14.2.9 the code running under Scheduler 4.3.8 now breaks.
public onSchedulerEvents(event: any) {
/* we need to catch these events before they are finalized (in the the graph) so
that we can cancel them if they are not validated by the server
*/
switch (event.type) {
case 'beforeeventdropfinalize':
case 'beforeeventresizefinalize':
. . .
event.context.async = true;
...
valid = ... validate(...
event.context.finalize(valid);
When dropping or resizing the event.context.startDate is correct, but event.context.endDate has the same value as the startdate.
And the eventRecord(s) do not contain updated values.
How did you configure your eventDrag feature? As you see from y screenshot, I do not get that result. The startDate and endDate in the context re both correct
Are you able to set up the configuration that you have in your project with a sample of data in an example project?? With that, would be easier for us to assist you, as we're not able to reproduce the behavior that you're mentioning in our demos.
Resizing an event will show the correct startdate and enddate.
Dragging an event will show the start date value in both the startdate and enddate.
This is my time resolution:
timeResolution: {
unit: 'day',
increment: 1,
},
My events are days or weeks long.
Another disturbing thing.
In version 5.2.3 I get the newResorce object whether I dragged the event to another resource or not.
And if I do change resource, newResorce is incorrectly populated
The new resource is now in both newResorce.data and newResorce.originalData, so I have no way of validating the change.
Please see video attached. We cannot reproduce the issue. Please create a runnable test case and attach it here, so we will be able to debug it and confirm a bug or find a reason of unexpected behaviour.