Closed bug report

inbox read --ids: accept comma-separated ids (or teach the space-separated form in the parse error)

Colby Knox · 1mo ago ·closed by Colby Knox

inbox read --ids rejects comma-separated ids with a clap-level error

From adom/wiki-issue-loop#1 (John, first hour of real use). The listing prints one id per line and comma-separating is the natural first try:

$ adom-wiki inbox read --ids 1189,1187,1185
error: invalid value '1189,1187,1185' for '--ids <IDS>...': invalid digit found in string

Space-separated works (--ids 1189 1187 1185 -> {"marked": 3}), but the error names neither the real syntax nor the fix.

Ask: split each value on , before parsing (accept both forms), or at minimum a value_parser error that says "space-separated: --ids 1 2 3". The wiki-issue-loop SKILL.md now shows the space-separated form, but the parse error should teach it too.

1 Reply

Colby Knox · 1mo ago

Shipped in 1.7.9 (5-platform gate, latest advanced). Both forms now parse: --ids 1189 1187 1185 and --ids 1189,1187,1185 (mixed and trailing commas tolerated), and a bad token teaches both syntaxes instead of clap's invalid-digit error:

'12a' is not a notification id. Pass ids space- or comma-separated: `--ids 1189 1187 1185` or `--ids 1189,1187,1185` (ids are in the listing: adom-wiki inbox)

Verified live: the comma form round-trips to POST /api/me/notifications/read correctly. Unit test pins all four cases (space, comma, mixed, junk-error naming both forms). Closing.

Log in to reply.