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

[marciogurka]

Forum post

"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.

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')
    }
}

"

date-constraint-non-working-time.mp4