[REACT] Recurrent event dont work

[wicher]

Hi!

Im trying to setup recurrent events to the scheduler but something clearly doesnt work. Only original starting event is displayed. I followed this thread viewtopic.php?t=13669 and added recurrenceRule to my event model, also tried just adding that property directly to the mocked data, to no success.

Ive extracted scheduler to a separate project for a reference, pls take a look https://drive.google.com/file/d/1ZiykvA5rJRNUdfhK7HqY_fjCEPbwtVlj/view?usp=share_link

[marcio]

Hey wicher,

Thanks for the example project, checking it looks like a bug, I created a ticket to fix that https://github.com/bryntum/support/issues/7708

[Animal]

I changed the example app to use that data format:

Screenshot 2023-10-19 at 18.39.29.png (1.15 MiB) Viewed 1855 times

As you can see, the events all recur as requested.

I cannot run that app attached. I just had to make the existing example use data in the same format.

[wicher]

Thx for such quick response!
Hm, so perhaps there is something wrong with our config.
:0 Why cant you run the app? I removed node modules to make project smaller, so all dependencies need to be installed, but it should run. Could you maybe take a look at the config in the project?

[Animal]

None of the "npm run" things work:

Screenshot 2023-10-20 at 06.41.04.png (177.29 KiB) Viewed 1829 times

[wicher]

hi!
Could you try npm install and then npm start?

[Animal]

That got this:

Screenshot 2023-10-20 at 11.16.11.png (760.61 KiB) Viewed 1816 times

What if you cut your project down to the minimal?

Just one simple new Scheduler({...}) statement to test out your data format?

[wicher]

https://drive.google.com/file/d/1ZiykvA5rJRNUdfhK7HqY_fjCEPbwtVlj/view?usp=share_link
Ive updated the project and removed package-lock.json. That should solve the problem, if not pls try npm cache clean --force and npm install again.

The project is already as small as can be to reflect setup in our app :C

Thx for all help

[kronaemmanuel]

Hi wicher,

I've created a Github issue to track this bug: https://github.com/bryntum/support/issues/7717. You can subscribe to the issue for more updates.

Regards,
Krona