-
Notifications
You must be signed in to change notification settings - Fork 247
Fix issue with BYWEEKNO=1 where UNTIL lies in the year prior to the year of the week of the last occurrence.
#752
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
Conversation
…r to the year of the week of the last occurrence.
Codecov ReportAttention: Patch coverage is
❌ Your project status has failed because the head coverage (66%) is below the target coverage (80%). You can increase the head coverage or adjust the target coverage. @@ Coverage Diff @@
## main #752 +/- ##
===================================
Coverage 66% 66%
===================================
Files 104 104
Lines 4611 4617 +6
Branches 1146 1147 +1
===================================
+ Hits 3047 3055 +8
Misses 1129 1129
+ Partials 435 433 -2
... and 2 files with indirect coverage changes 🚀 New features to boost your workflow:
|
2a297a0 to
dee8ef0
Compare
…he year of the week of the last occurrence.
dee8ef0 to
5504cb4
Compare
|
axunonb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another edge case fixed, very good
| } | ||
| } | ||
|
|
||
| private static CalDateTime? GetSearchEndDate(CalDateTime? periodEnd, RecurrencePattern pattern) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍



In cases where
BYWEEKNO=1is specified, week no 1 may start in the year prior to the one it belongs to. If both, the last occurrence andUNTILlie in the year prior to the year the corresponding week belongs to,UNTILhas not been handled correctly, which is fixed with this PR.E.g. the following case is fixed, which was missing the last instance prior to the fix:
fixes #751