Calendar: the Android rule-change confirm counts what it changes #266

New issue

Open

opened 2026-08-26 08:19:53 +00:00 by nalum · 0 comments

nalum commented

2026-08-26 08:19:53 +00:00

Owner

The web's rule-change confirm counts the real consequences before asking — it lists the repeating event's children over the wire (splits and tombstones via listEvents) and names the count in the dialog. The Android sheet asks the same question generically ("this changes future occurrences") because the counting query wasn't brought across in PR #263.

This was a recorded divergence at delivery time (calendar handoff §5, the rule-change confirm). Bring the Compose sheet up to the web's wording: same query, same counted sentence, pinned by the conformance fixture once the event-sheet fixture family exists.

The web's rule-change confirm counts the real consequences before asking — it lists the repeating event's children over the wire (splits and tombstones via `listEvents`) and names the count in the dialog. The Android sheet asks the same question generically ("this changes future occurrences") because the counting query wasn't brought across in PR #263. This was a recorded divergence at delivery time (calendar handoff §5, the rule-change confirm). Bring the Compose sheet up to the web's wording: same query, same counted sentence, pinned by the conformance fixture once the event-sheet fixture family exists.

nalum referenced this issue

2026-08-26 08:58:54 +00:00

fix(calendar): the polish round — review fixes and the revised handoff #268

nalum referenced this issue

2026-08-26 18:48:02 +00:00

Calendar: scope, the rule-change confirm, cancelling and deleting #196

nalum referenced this issue

2026-08-26 18:48:03 +00:00

Order of work for the calendar redesign (#187-#198) #199

nalum added the

android

area/calendar