fix(dav): include duration in recurring event range - #64393
abhinavohri wants to merge 1 commit into
Conversation
Include the final occurrence duration when deriving the searchable time range for recurring calendar objects. Assisted-by: Codex:gpt-5 Signed-off-by: Abhinav Ohri <abhinavohri13@gmail.com>
|
already addressed in #64315 Closing as duplicate |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
Summary
This PR fixes a bug where recurring events used the final occurrence's start time as
lastoccurenceinstead of its end time. This caused appointment searches overlapping the final occurrence to skip the event and incorrectly expose the time slot as available.The change calculates the duration of an occurrence before processing
RDATEandRRULE, then adds that duration to the final occurrence's start time for finite recurrences.Checklist
3. to review, feature component)stable32)AI (if applicable)