Open Programie opened 9 months ago
As this is still an issue, I've looked for a workaround and found a way to check whether the event is a non-all-day event while the start and end times are the same.
It's quite easy but I didn't saw that before: Just check whether durationSeconds
is zero. If that's the case, the event should not be an all-day event. Checking whether eventStart
and eventEnd
are the same should also work, but I guess it could have different values if eventStart
and eventEnd
use different time zones.
Describe the bug I have some events which don't have an end-date (i.e. the end date is the same as the start date). Every calendar application is correctly handling that event as a non-all-day event. But in case of this Node-RED module, those events are flagged as all-day events (i.e.
allDay
of those events is set totrue
).To Reproduce Steps to reproduce the behavior:
allDay: true
for the previously created non-all-day eventExpected behavior The event should have
allDay: false
in case the event is not an all-day event.node-red-contrib-ical-events
Logs / Additional context Example calendar file:
JSON output from the "upcoming" node: