Period record CRUD: add, edit and delete a confirmed period #6

Closed
opened 2026-08-18 02:14:37 -05:00 by null · 0 comments
Owner

The first thing the app must be able to do, and the last piece of Batch 01. PRODUCT_PLAN.md §58 names the vertical slice this completes: enter period starts, store them, recalculate, show the result.

What this covers:

  • add a confirmed period with a start date, and optionally an end date
  • edit an existing record, recording that it was edited (PeriodRecordSource.EDITED) rather than silently changing it
  • delete a record
  • every one of those triggers a recalculation, so the forecast on screen is never stale relative to the data

This is not the Today screen. The designed Today screen and its six dynamic states are Batch 03; what is needed here is a plain surface that exercises the loop end to end, and it should look unfinished so nobody mistakes it for the real one. A convincing mock is how a screen comes to be believed finished.

Depends on the repository issue in this batch.

Verify: on a device, adding three period starts produces a forecast that changes when a record is edited and again when one is deleted; the records survive a force-stop; and ./gradlew test passes.

The first thing the app must be able to do, and the last piece of Batch 01. PRODUCT_PLAN.md §58 names the vertical slice this completes: enter period starts, store them, recalculate, show the result. What this covers: - add a confirmed period with a start date, and optionally an end date - edit an existing record, recording that it was edited (`PeriodRecordSource.EDITED`) rather than silently changing it - delete a record - every one of those triggers a recalculation, so the forecast on screen is never stale relative to the data **This is not the Today screen.** The designed Today screen and its six dynamic states are Batch 03; what is needed here is a plain surface that exercises the loop end to end, and it should look unfinished so nobody mistakes it for the real one. A convincing mock is how a screen comes to be believed finished. Depends on the repository issue in this batch. Verify: on a device, adding three period starts produces a forecast that changes when a record is edited and again when one is deleted; the records survive a force-stop; and `./gradlew test` passes.
null added this to the Batch 01 — Foundation milestone 2026-08-18 02:14:37 -05:00
null closed this issue 2026-08-18 02:52:39 -05:00
Sign in to join this conversation.
No Label
P0
P1
P2
release-blocker
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: null/Privacy-Period-Tracker#6
No description provided.