Our pure JavaScript Scheduler component


Post by bizzcoo »

Hello,

I use Scheduler Pro 4.0.0.
When using the ES module bundle I get the following error

Uncaught (in promise) TypeError: startDate.getTime is not a function
    at CalendarCacheMultiple.forEachAvailabilityInterval (schedulerpro.module.js:99635)
    at ClassDefEx.forEachAvailabilityInterval (schedulerpro.module.js:151677)
    at forEachAvailabilityInterval.next (<anonymous>)
    at ClassDefEx.skipNonWorkingTime (schedulerpro.module.js:151735)
    at skipNonWorkingTime.next (<anonymous>)
    at ClassDefEx.calculateStartDateProposed (schedulerpro.module.js:109783)
    at calculateStartDateProposed.next (<anonymous>)
    at ClassDefEx.calculateStartDateProposed (schedulerpro.module.js:135384)
    at calculateStartDateProposed.next (<anonymous>)
    at ClassDefEx.calculateStartDateProposed (schedulerpro.module.js:151034) 

I have tried importing it in different ways,

import { SchedulerPro } from 'bryntum-schedulerpro';
import { SchedulerPro } from 'bryntum-schedulerpro/schedulerpro.module.js';
import { SchedulerPro } from '../../../scheduler-pro/build/schedulerpro.module.js';

but all result in the error above.

When resizing the browser window, the events sometimes show briefly but then disappear again.

When using the umd version import it works fine, however I would like to use the ES module bundle.

I can't seem to find what causes this error so any help or pointers towards what I'm missing and doing wrong here is much appreciated.

I have included the Angular project I used for testing this.

Attachments
scheduler-pro-esm.zip
(139.91 KiB) Downloaded 87 times

Post by alex.l »

Hi bizzcoo,

Thanks for your report and the test case! I was able to reproduce it and it looks like a bug. Here is a ticket: https://github.com/bryntum/support/issues/1803
Meanwhile, please use schedulerpro.lite.umd.js before we fix this problem.

All best,
Alex

All the best,
Alex


Post Reply