[SchedulerPro] Date constraints are not respected when used together with non-working time

[jamesb]

Hi Bryntum Team,

We noticed that when a date constraint ends within a non-working time interval, then an event dropped at the constraint end date can extend past the end date.

Here's a video of the issue:

date-constraint-non-working-time.mp4

(942.66 KiB) Downloaded 26 times

All events are constrained to end on or before 7PM on March 23rd, but after the drop they end on March 24th.

It can be reproduced on the resource-non-working-time example, by adding the configuration below: https://bryntum.com/products/schedulerpro/examples/resource-non-working-time/

getDateConstraints() {
    return { 
        start: new Date('2020-03-23T07:00'),
        end: new Date('2020-03-23T19:00')
    }
}

Thank you for your help,
J

[marcio]

Hey J,

Thanks for the report and example, we'll be looking into that in this ticket https://github.com/bryntum/support/issues/6897