Skip to content

docs(api): daily audit 2026-09-30 — alert detail_url into the rendered on-call spec, RUM issue-detail team_id semantics - #778

Merged
ysyneu merged 3 commits into
mainfrom
api-review/20260930T160733Z
Oct 6, 2026
Merged

ysyneu merged 3 commits into
mainfrom
api-review/20260930T160733Z

Conversation

@flashduty

@flashduty flashduty Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

Daily OpenAPI sync: alert detail_url in the rendered on-call spec, and RUM issue-detail team_id semantics (zh + en, module and consolidated). Lint clean.

…d on-call spec, RUM issue-detail team_id semantics

Two changes, both derived from the source repos at origin/main.

B. on-call AlertItem / AlertInfo gain `detail_url`.
   fc-event structs/alert.go:74-78 — `DetailUrl string `json:"detail_url,omitempty"``,
   filled at read time, empty when the deployment has no console base. The
   consolidated specs got the field on 2026-09-29 (4b9015a) but the per-module
   split files — the ones Mintlify renders — never did, so POST /alert/info
   documented no detail_url on the docs site.

A. POST /rum/issue/info documents that `team_id` is the application's current team.
   fc-rum cmd/server/controller/issue/info.go:221 `item.TeamID = application.TeamID`
   (PR #230, merge a190844, 2026-09-29). Issue rows keep the team recorded at
   creation (logic/transfer.go:55), which is what list and export still report.
@ysyneu
ysyneu merged commit e51d50b into main Oct 6, 2026
2 checks passed
@ysyneu
ysyneu deleted the api-review/20260930T160733Z branch October 6, 2026 03:06
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