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

Repeating Events hard to handle #113

Open
Logianer opened this issue May 10, 2021 · 3 comments
Open

Repeating Events hard to handle #113

Logianer opened this issue May 10, 2021 · 3 comments

Comments

@Logianer
Copy link

I wish for a better way to handle repeaing events in the parser like parsing the repeating events as a seperate object and not having only one with the attributes...idk but it's hard to detect when a repeated event takes place. You only have the original wich says yea...i repeat but you have to manage it yourself..

@jens-maus
Copy link
Owner

Feel free to submit a PR with improvements!

@sdetweil
Copy link
Contributor

@Logianer IF the parsed event has an RRULE attribute, then YOU must call one of the RRULE methods to get the list of future events that match that rule. node-ical does not do that... as there are different options available.

our app calls rrule.between(start_range, end_range)

@sdetweil
Copy link
Contributor

AND rrule.between() only deals w local time, no tz
if you DO NOT CONVERT, you WILL get events W WRONG DATE but correct time.

SO you have to convert ALL the node-ical parsed dates to local time start/end, rrule, exdates and recurrences

AND then back if your app handles tz based events

finally have our app correctly handling events

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

3 participants