You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create unit tests to check whether we can read the iCal/ICS files correctly and correctly interpret the data in it.
That means reading it in an Event object, writing it out as JSCalendar JSON object, and comparing the result with the expected result.
This should be based on test cases supplied by others, en masse.
I haven't looked to see how the messages are used, so it's possible that some of them have deliberate errors.
1 has a malformed METHOD
2 have a malformed DTSTART
3 have a malformed DTEND
None of the reply and cancel messages bother filling in the whole event; they only provide the UID and ATTENDEEs. I haven't checked to see whether this is permitted.
I found some code errors; I don't know whether it's worth creating individual PRs for each of these.
We aren't parsing the recurrence rule case-insensitively (as it happens all of the test cases were already in upper case)
Stringifying the recurrence rule should use the allDay format as appropriate
The wrong variable is being used to check for the organiser being a participant
It is possible for the organiser to match against multiple participants
Of the rest of the sample files, most weren't in a format that looked like an invitation, so I'm not sure how useful they are as a test, but I was able to adapt a few more, which led me to discover that all day events weren't being properly recognised,
Create unit tests to check whether we can read the iCal/ICS files correctly and correctly interpret the data in it.
That means reading it in an
Event
object, writing it out as JSCalendar JSON object, and comparing the result with the expected result.This should be based on test cases supplied by others, en masse.
Potential sources:
Pay attention for licenses, please.
Other parsers or resources:
The text was updated successfully, but these errors were encountered: