-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use DTSTART when BY* is missing #434
Comments
|
It should be derivered for |
Just checking in on this, @radarfox have you had a chance to take a closer look if any additional action is needed here? Would also appreciate a retest on the latest version. |
It looks like we haven't heard back on this issue, therefore we are closing this issue. If this problem persists in the latest version of ical.js, please re-open this issue. |
Hello,
I think I have found the bug in this library, that has not been covered by any other issue here.
From the RFC 5545 3.3.10:
This isn't happening, at least with BYMONTH and BYMONTHDAY, as I have tested. The full list of BY* rules that should use this is: BYMONTH, BYMONTHDAY, BYDAY, BYHOUR, BYMINUTE and BYSECOND.
For example the following calendar has the single event. In this event the YEARLY frequency is defined and the day is second Friday, but the month is not explicitly mentioned. In this case, according to the RFC, the DTSTART should be used and the occurrences should be in August.
I would expect the occurrences to be in August:
But this isn't happening, the occurrences are in January:
From these values I think it's clear, that
ICAL.Recur
is using January, when the BYMONTH is not explicitly defined. By this rule the first occurrence makes sense, the 20210108 is the 2nd Friday of January after 20200814.If the BYMONTH is defined, then occurrences are as expected:
The text was updated successfully, but these errors were encountered: