Drag and drop on same day does not update time in custom title formatter

[tim-faase]

Describe the bug

Dragging an event on week view within the same day does not update the time shown in custom title formatter.

Minimal reproduction of the problem with instructions

https://stackblitz.com/edit/angular-wm4ozr

Screenshots

Versions

• @angular/core: 9.1.1
• angular-calendar: 0.28.8
• Browser name and version: Version 81.0.4044.122 (Official Build) (64-bit)

[matts-bot]

Thanks so much for opening an issue! If you'd like me to give priority to answering your issue or would just like to support this project, then please consider sponsoring me

[mattlewis92]

Hey, thanks for reporting! I'm kind of amazed this has never come up before, I will do my best to find a way of fixing it 😄

[mattlewis92]

Please can you give 0.28.13 a go, it should be fixed now, thanks for reporting! 😄

[tim-faase]

Thank you matt! It took me a few hours to find the cause, our app wasn't working but Stackblitz example did, this fix works with snapDraggedEvents property set to true, with it set to false it doesn't work I'm afraid.
Appreciate all your work on this open source component.

[mattlewis92]

Ahh I didn't consider that, it's because the drag and drop library uses cloneNode on the element so it won't be updated while dragging, I think I can fix it pretty easily

[mattlewis92]

Please give 0.28.15 a go, it should be fixed now 😄

[tim-faase]

If you weren't so nice I might not be posting this! 😄 it has occurred to me twice; that a mismatch of @angular/core to your latest release causes drag and drop to stop working in --prod. ng serve is fine but once I build it to production with the flag the cells don't accept an eternal event.

[mattlewis92]

If you weren't so nice I might not be posting this! 😄 it has occurred to me twice; that a mismatch of @angular/core to your latest release causes drag and drop to stop working in --prod. ng serve is fine but once I build it to production with the flag the cells don't accept an eternal event.

Sounds more like a bug with angular itself rather than anything this library is doing, but if you can make a minimal repro on github that shows the problem then I can investigate further. Thanks!