-
Notifications
You must be signed in to change notification settings - Fork 47
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
BYSETPOS and unsynchronized start dates #75
Comments
dmfs
added a commit
that referenced
this issue
Nov 6, 2022
Looks like there is nothing to do because it's already handled correctly, at elast when using `RecurrenceSet`. closes #75
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since
RecurenceRule
doesn't generate unsynchronized start dates anymore, theBYSETPOS
filter is most likely to generate "unexpected" results when being used with such a start. In particular, it will start counting from the first generated event, so the events of the first interval may be off by 1.Any solution to this should be optional, since there are use cases for the current behavior too.
The text was updated successfully, but these errors were encountered: