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
Don't generate all possible events #182
Comments
I guess in order to support this the |
Relates to #149 I do not think this is as simple as only processing a recurrence event for a desired range (beyond the start and end date defined by the rule). Although this may suit the given rule, other rules can be much more complex and require processing to be started from the beginning (rather than towards the end, 38 years on). What could be achieved is something similar to the As for the length of time it takes the parser to process your rule in its current version, it takes me The other possibility is to reduce the 38 years of calendar data you have which is only going to grow larger. |
Description of the Issue:
Given a recurrence event, it looks like ics-parser generates all possible events during the dates in the ics-file. In my case it creates 10,000 events and takes forever (and uses lots of memory) even though I'm only interested in events for a limited range. Would it be possible to just generate the events for the supplied range instead?
I'm thinking it should be possible to just generate events for the range given in
->eventsFromRange(start, end)
.Steps to Reproduce:
The text was updated successfully, but these errors were encountered: