Skip to content

Fix advancement for earlier moved Google Calendar occurrences - #2191

Open
martin-forge wants to merge 1 commit into
callumalpass:mainfrom
martin-forge:martin-forge/fix-moved-recurrence-advance
Open

Fix advancement for earlier moved Google Calendar occurrences#2191
martin-forge wants to merge 1 commit into
callumalpass:mainfrom
martin-forge:martin-forge/fix-moved-recurrence-advance

Conversation

@martin-forge

@martin-forge martin-forge commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Problem

A moved occurrence replaces its original recurrence slot, but next-occurrence planning ignored that stored exclusion. Completing or skipping a weekly occurrence moved from 13 April to 10 April could therefore schedule 13 April again. In a daily series, the excluded date could reappear after intervening occurrences.

Fix

Include pending and resolved moved-original dates only while calculating the next open occurrence. Persisted completion and skip history remains keyed to the moved date.

Expected sequences:

  • Weekly, 13 April moved to 10 April: completing or skipping 10 April advances to 20 April.
  • Daily, 13 April moved to 10 April: subsequent dates are 11, 12, then 14 April. The replaced 13 April occurrence does not reappear.

Validation

  • Focused recurrence-planning tests: 16 passed
  • Related recurrence and Calendar tests: 77 passed
  • Lint, architecture checks, type-check, and production build passed

@martin-forge
martin-forge force-pushed the martin-forge/fix-moved-recurrence-advance branch from 94cdac7 to 55d5e7b Compare August 3, 2026 13:46
@martin-forge
martin-forge force-pushed the martin-forge/fix-moved-recurrence-advance branch from 55d5e7b to 4006d63 Compare August 3, 2026 14:21
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