Google Calendar ical `EXDATE not correctly parsed
Closed this issue · 3 comments
Fix007 commented
Google Calendar's implementation of EXDATE
does not follow the specification. Instead of comma-separated datetimes, each EXDATE
is written to a new line.
Therefore only the last EXDATE
is in the parsed object.
Example:
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20221205T000000
DTEND;TZID=Europe/Berlin:20221205T020000
RRULE:FREQ=DAILY
EXDATE;TZID=Europe/Berlin:20221210T000000
EXDATE;TZID=Europe/Berlin:20221208T000000
DTSTAMP:20221206T203724Z
UID:6vui5pik8466jo53fhh503ssd9@google.com
CREATED:20221206T102926Z
LAST-MODIFIED:20221206T102926Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Just a quick summary
TRANSP:OPAQUE
END:VEVENT
TesteurManiak commented
I'll look into it whenever I can, for the time being you can try overriding the parsing logic for the field with the methods unregisterField
and registerField
.
TesteurManiak commented
Your issue should be fixed and the package has been published under the version 1.1.0
on pub.dev.
Fix007 commented
Thank you
Works without problems