bug(issues): list --since/--before reject date-only input that the help's own example uses #91

New issue

Closed

opened 2026-07-15 14:47:45 +00:00 by hexajon · 0 comments

hexajon commented

2026-07-15 14:47:45 +00:00

(Migrated from codeberg.org)

Observed 2026-07-15: madtea issue list --state all --since 2026-07-15 → API error 422: parsing time "2026-07-15" as "2006-01-02T15:04:05Z07:00": cannot parse "" as "T" — the raw server parse error surfaces verbatim. But madtea issue list --help itself shows a date-only example: madtea issue list --before 2026-01-01, which fails the same way.

Fix: normalize date-only input client-side (YYYY-MM-DD → YYYY-MM-DDT00:00:00Z, and arguably end-of-day for --before) before hitting the API, so both flags accept what the help advertises. Failing that, fix the help example and translate the 422 into an actionable message naming the expected format. Same check for any other tools/flags that pass timestamps through (MCP issues_list equivalents).

Observed 2026-07-15: `madtea issue list --state all --since 2026-07-15` → `API error 422: parsing time "2026-07-15" as "2006-01-02T15:04:05Z07:00": cannot parse "" as "T"` — the raw server parse error surfaces verbatim. But `madtea issue list --help` itself shows a date-only example: `madtea issue list --before 2026-01-01`, which fails the same way. Fix: normalize date-only input client-side (`YYYY-MM-DD` → `YYYY-MM-DDT00:00:00Z`, and arguably end-of-day for --before) before hitting the API, so both flags accept what the help advertises. Failing that, fix the help example and translate the 422 into an actionable message naming the expected format. Same check for any other tools/flags that pass timestamps through (MCP issues_list equivalents).

No milestone

No project

No assignees

1 participant

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

sixfold-space/madtea#91

No description provided.

Rows
Columns