Skip to content
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

Invalid parse support of the EXDATE attribute #191

Open
oc-clem opened this issue Jul 7, 2021 · 0 comments
Open

Invalid parse support of the EXDATE attribute #191

oc-clem opened this issue Jul 7, 2021 · 0 comments

Comments

@oc-clem
Copy link

oc-clem commented Jul 7, 2021

Hi there 👋,

First of all, thank you for this library, it helps a lot!

I encountered an issue while working with excluded dates.
I noticed a format difference between the RFC and the actual implementation while parsing the recurrence string.

According to the RFC 5545, the EXDATE should be written on a new line like this:

DTSTART:20210622T120000Z
RRULE:FREQ=WEEKLY;BYDAY=TU;UNTIL=20210712T120000Z
EXDATE:20210629T120000Z,20210706T120000Z

But, when I load this string in a new Rule(), it does not handle the excluded dates.
The Rule constructor expects an EXDATE like this:

DTSTART:20210622T120000Z
RRULE:FREQ=WEEKLY;BYDAY=TU;UNTIL=20210712T120000Z;EXDATE=20210629T120000Z,20210706T120000Z

For now, I used str_replace() to convert these excluded dates, but it could be great if the library auto handles both formats.

Thanks a lot and have a nice day!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant