Skip to content

fix(incident): fetch get by id through /incident/list-by-ids - #215

Merged
ysyneu merged 2 commits into
mainfrom
feat/incident-get
Oct 9, 2026
Merged

ysyneu merged 2 commits into
mainfrom
feat/incident-get

Conversation

@ysyneu

@ysyneu ysyneu commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Promotes #214 to main for the v1.5.13 release.

incident get <id>... sent only incident_ids to POST /incident/list, which requires start_time/end_time, so every call returned HTTP 400. It now fetches through POST /incident/list-by-ids; short-id resolution still uses /incident/list with its 30-day lookback. Verified against a live dev backend (single, short and multi id; json and table). Details in #214.

🤖 Generated with Claude Code

ysyneu added 2 commits October 8, 2026 22:27
`incident get <id>...` sent only incident_ids to /incident/list. That
endpoint requires a start_time/end_time window, so every call failed with
"StartTime is a required field, EndTime is a required field" (HTTP 400).

Fetch through /incident/list-by-ids, which takes ids alone and returns the
same row shape. Short-id resolution still goes through /incident/list with
its 30-day lookback. Tests now assert the request path, which the previous
stub did not check.
fix(incident): fetch `get` by id through /incident/list-by-ids
@ysyneu
ysyneu merged commit c85ec90 into main Oct 9, 2026
12 checks passed
@ysyneu
ysyneu deleted the feat/incident-get branch October 9, 2026 05:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant