chore(ui): regenerate openapi schema for Plan 02 alerting endpoints #143
Reference in New Issue
Block a user
Delete Branch "chore/openapi-regen-post-plan02"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Regenerated
ui/src/api/openapi.json+ui/src/api/schema.d.tsagainst the deployed Plan 02 backend athttp://192.168.50.86:30090/api/v1/api-docsvianpm run generate-api:live. Unblocks Plan 03 UI work.Net: +1,416 / −91 across 2 files (types + JSON).
New TypeScript paths now available
/environments/{envSlug}/alerts/**— rules CRUD, enable/disable, render-preview, test-evaluate, inbox list, unread-count, single alert, ack/read/bulk-read, silences CRUD, per-alert notifications list./alerts/notifications/{id}/retry(notification IDs are globally unique; documented in the flat-allow-list).Verification
cd ui && npx tsc -p tsconfig.app.json --noEmit— exits 0. No existing SPA call sites break against the fresh types.npm run generate-api:livepicked up the script's pre-configured URL — no manual URL munging.Impact
Pure doc/types regen; no runtime code touched. Plan 03's UI can import from the regenerated
schema.d.tsfrom commit one.