Skip to content

Fix/vtodo completed only range check - #11

Merged
tobixen merged 2 commits into
mainfrom
fix/vtodo-completed-only-range-check
May 27, 2026
Merged

Fix/vtodo completed only range check#11
tobixen merged 2 commits into
mainfrom
fix/vtodo-completed-only-range-check

Conversation

@tobixen

@tobixen tobixen commented May 22, 2026

Copy link
Copy Markdown
Member

Edit: The second commit is vibed up en-passant while trying to import some broken icalendar data into my calendar. It needs proper review and probably rebasing/rewording before it's merged.

The first commit seems to be orphaned work, maybe it needs a separate pull request, or maybe it should be dropped. I'll look into it.

@tobixen
tobixen marked this pull request as draft May 22, 2026 09:48
@tobixen
tobixen force-pushed the fix/vtodo-completed-only-range-check branch 2 times, most recently from dfbda20 to 5b5ff47 Compare May 22, 2026 22:41
tobixen and others added 2 commits May 27, 2026 21:30
Doing time filtering on a VTODO with a COMPLETED, but no DTSTART, DUE,
or CREATED, things would crash.

This was discovered a bit ad-hoc while importing some slightly broken
icalendar data into a calendar, and Claude had a go on fixing it.

Also, I reread RFC4791 section 9.9 and had Claude reread it again, and
now I think all the corner cases are covered according to the RFC.

prompt: (work on some unrelated stuff and asking Claude to investigate the crash)
(I rewrote Clauds work completely)
prompt: tests are broken with my last changes, but please verify if the
correct thing is asserted. As I understand the relevant RFC-section, a
VTODO with CREATED set but no other time-related properties should match
if and only if the search interval covers the CREATED timestamp.
followup-prompt: and read through section 9.9 in the caldav RFC as well.
(claude concluded my new code was not in accordance with the RFC, the
pre-existing assert in the test code is in accordance with the RFC, and the
code section was rewritten for the second time)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@tobixen
tobixen force-pushed the fix/vtodo-completed-only-range-check branch from 5b5ff47 to b3a28e1 Compare May 27, 2026 19:36
@tobixen
tobixen marked this pull request as ready for review May 27, 2026 20:16
@tobixen
tobixen merged commit 7393a22 into main May 27, 2026
12 checks passed
@tobixen
tobixen deleted the fix/vtodo-completed-only-range-check branch May 29, 2026 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant