Closed ghulamghousdev closed 2 months ago
Thank you, Blocking us from upgrading to 6.X
Checking this now!
It seems moving the 2nd event in the series (and choosing "only this event") actually re-assigns the whole series.
any updates on the release cycle?
We release patch releases every 2-4 weeks typically, so expect this to roll out sometime next w.
Forum post
Hi,
I encountered an issue with the reassignment of one event of a series to another resource when using the CrudManager in Calendar 6.0.2.
When changing the assigned resource of a recurring event and selecting the "only this event" option in the dialog, the CrudManager sends unexpected operations. Typically, when selecting "only this event" I expect an "update" operation which excludes the changed event date from the original series and an "add" event which creates a new event with the newly assigned resource. This also works as expected but only for the first event of a series. When changing the resource of the second event of the series, only one "update" Crud operation is being sent.
This unexpected behavior only happens when changing an event within a series (not the first event) and only when changing ONLY the assigned resource via drag-and-drop. When changing the startDate along with the assigned resource, the Crud operations are generated as expected.
Attached you will find a working example. Please start the frontend and backend, reassign the event "Hackathon 2020" on the 21.10.2020 to another resource (keeping the same date/time) and select "only this event" and watch the network tab.
When doing the steps for the first event in the recurrent series:
https://github.com/user-attachments/assets/7682937a-6058-4752-9c8b-6cebd4172203
When changing the resource for the any other event then first in the recurrent series, no new event is added and incorrect update request:
https://github.com/user-attachments/assets/13a1a6f0-8cc1-43e0-9f8d-ff8e682283eb
Test Case: calendar-angular-basic-crud-change-resource.zip