-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
Wrong recurrence handling #196 #231
Comments
I have no plans to change how the parser returns recurrence events.
If the parser is incorrectly parsing an ICS file I would be happy to take a look. |
I don't know whether it's incorrect, but at least it's very unexpected. Take the ics file from the old issue as an example: But the ics-parser will return 7 events: If someone parses those 7 events and their rrules to fill a calendar or anything like this, it will result in multiple identical events from the second day on (2 events on 2nd day, 3 events on 3rd day, 4 events on 4th day, ...) |
Happy to review a draft PR with a change to the current behaviour if you want to pull something together. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm happy with the current implementation so closing for now |
Hello,
I didn't work on this topic for a while, but now I'm back. This issue is the follow-up to #196 as this was closed and I cannot reopen it.
I think my former posts were unclear. What I wanted to say is that, in my opinion, the parser should either return an event for each day without rrule or one single event for all days with an rrule.
Currently it returns one event for each day and each of those events has an rrule field. If one considers the rrule it leads to multiple events on the same day, e.g. 2 events on 2nd day, 3 events on 3rd day and so on.
The text was updated successfully, but these errors were encountered: