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.

Sign up for GitHub

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

Jump to bottom

BYSETPOS and unsynchronized start dates #75

Open
dmfs opened this issue Apr 8, 2020 · 0 comments
Open

BYSETPOS and unsynchronized start dates #75

dmfs opened this issue Apr 8, 2020 · 0 comments

Comments

@dmfs
Copy link
Owner

dmfs commented Apr 8, 2020

Since RecurenceRule doesn't generate unsynchronized start dates anymore, the BYSETPOS 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.
dmfs added a commit that referenced this issue Nov 6, 2022
@dmfs
Add test case for #75
09a2b6d 
Looks like there is nothing to do because it's already handled
correctly, at elast when using `RecurrenceSet`.

closes #75
@dmfs dmfs mentioned this issue Nov 6, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add test case for #75 dmfs/lib-recur
1 participant
@dmfs