Todo Update Due Date Not Working

[armand-fourie-savino]

Problem

Running basecamp todos update <id> --due 2026-04-12 --json doe does not update actual due_on date:

• Response returns OK, with updated message
• due_on remains unchanged

Basecamp CLI version

basecamp version 0.7.2

[josuhr]

Confirming this on 0.7.2 (macOS, arm64).

Key detail that may help narrow it down: the due date does apply correctly on creation — basecamp todo "Task" --due 2026-07-31 returns due_on: "2026-07-31". The bug appears isolated to the todos update path.

Additional observations:

• Fails with both --due 2026-07-31 and natural language (--due tomorrow) — response is ok: true but due_on stays null.
• todos update --assignee works and, importantly, does not wipe an existing due_on. So the update path handles assignees correctly but drops due_on specifically.

Workaround until fixed: set the due date at creation time rather than via update.

[crsmoore]

Confirming similar behavior on basecamp version 0.7.2.

I tested both an ISO date and natural language:

basecamp todos update <todo-id> --due 2026-05-25 --json
basecamp todos update <todo-id> --due tomorrow --json

Both commands returned success (ok: true / Updated todo), but checking the raw todo afterward still showed:

"due_on": null

Using the bucket-scoped raw API endpoint did persist the due date:

basecamp api put buckets/<bucket-id>/todos/<todo-id>.json \
 -d '{"content":"Test todo","description":"","assignee_ids":[<person-id>],"due_on":"2026-05-25"}' \
 --json

After that, the raw API response showed:

"due_on": "2026-05-25"

One related observation: the todos update --due attempt also cleared the existing assignee on my test to-do. So this looks related to the partial-update field preservation issue covered by #413.