feat: todos update --description flag does not persist changes

[ridhaaulia]

Bug Report

Command

basecamp todos update <id> --description "..." --in <project>

Expected behavior

The todo's description is updated with the new content.

Actual behavior

The command returns ok: true and shows the old description in the response — the new content is never saved. Verified by immediately fetching the todo after the update; the description is unchanged.

Reproduction

basecamp todos update 10116375130 --description "TEST UPDATE" --in 48125211 --json
# Response contains old description, not "TEST UPDATE"

# Confirm it didn't save:
basecamp todos show 10116375130 --in 48125211 --jq '.data.description'
# Still returns old content

Notes

- Passing the Basecamp URL instead of ID produces the same result
- --title, --due, --assignee all work correctly — only --description is affected
- The flag is documented in basecamp todos update --help and listed with usage "Extended description (Markdown)"

Environment

- CLI version: 0.7.2
- OS: macOS Darwin 24.5.0

[jeremy]

Thanks for the detailed report — the reproduction and the "only --description is affected" detail made this easy to pin down.

Root cause: in v0.7.2 a todos update --description ... edit sent a partial update body containing only the changed field. The Basecamp API's todo update (PUT .../todos/{id}.json) expects the full set of parameters, so a description-only body didn't take effect. --title/--due/--assignee happened to go through the same partial path but weren't affected in the same way.

Status: this is already fixed on main — #543 reworked todos update to a full read-modify-write that always sends the complete todo representation (content + description + the rest). It's covered by unit tests. The fix ships in the next release, which is in progress.

Could you confirm the CLI version you're on (basecamp --version)? If it's ≤ v0.7.2 this matches; once the next release lands, an update will resolve it. I'll leave this open until that release is out.

[ridhaaulia]

Yes, I just confirmed my CLI is on basecamp version 0.7.2, so that lines up with the issue you described. Thanks for the clear breakdown. I’ll go ahead and update to the new release once it ships tomorrow so the fix is included. Appreciate the info!