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

Wrong recurrence handling #196 #231

Closed
pikim opened this issue Aug 4, 2019 · 6 comments
Closed

Wrong recurrence handling #196 #231

pikim opened this issue Aug 4, 2019 · 6 comments

Comments

@pikim
Copy link

pikim commented Aug 4, 2019

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.

@u01jmg3 u01jmg3 self-assigned this Aug 6, 2019
@u01jmg3
Copy link
Owner

u01jmg3 commented Aug 6, 2019

the parser should either return an event for each day without rrule or one single event for all days with an rrule

I have no plans to change how the parser returns recurrence events.

it leads to multiple events on the same day, e.g. 2 events on 2nd day, 3 events on 3rd day and so on

If the parser is incorrectly parsing an ICS file I would be happy to take a look.

@pikim
Copy link
Author

pikim commented Aug 6, 2019

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:
Mainly there is one event in it with a daily RRULE. So this is just one event, repeated every day for one week, starting on the 5. of November, ending on the 11. of November.

But the ics-parser will return 7 events:
the first one starting on the 5. with a daily rrule until the 11.
the second one starting on the 6. with a daily rrule until the 11.
the third one starting on the 7. with a daily rrule until the 11.
the fourth one starting on the 8. with a daily rrule until the 11.
the fifth one starting on the 9. with a daily rrule until the 11.
and so on.

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, ...)

@u01jmg3
Copy link
Owner

u01jmg3 commented Aug 6, 2019

Happy to review a draft PR with a change to the current behaviour if you want to pull something together.

@Alexand3-R

This comment has been minimized.

@u01jmg3

This comment has been minimized.

@u01jmg3
Copy link
Owner

u01jmg3 commented Sep 10, 2019

I'm happy with the current implementation so closing for now

@u01jmg3 u01jmg3 closed this as completed Sep 10, 2019
@u01jmg3 u01jmg3 removed their assignment Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants