Move the alerts UI routes onto spec'd /qqq/v1 extension classes #13

Closed
opened 2026-10-14 00:14:21 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-14 00:14:21 +00:00 (Migrated from github.com)

api/AlertsRouteProvider.java:57-106 serves 7 raw /qqq/v1/alerts routes:

  • inbox summary, list, read, unread, dismiss;
  • record-panel, watch.

Port them to AbstractJsonEndpointSpec classes under the established prefix /alerts, then:

  • commit src/main/resources/openapi/qqq-v1/alerts.yaml with a contract test;
  • have payloads carry actions and hrefs, so Next stops hard-coding the alerts processes and tables.

This blocks the strict-mode flip (qqq G2). Follow collaboration#8 and data-analysis#5.

Source: Architecture review QRun-IO/qqq#1150 (docs/ARCHITECTURE-REVIEW-2026-10-13.md), finding F2.

`api/AlertsRouteProvider.java:57-106` serves 7 raw `/qqq/v1/alerts` routes: - inbox summary, list, read, unread, dismiss; - record-panel, watch. Port them to `AbstractJsonEndpointSpec` classes under the established prefix `/alerts`, then: - commit `src/main/resources/openapi/qqq-v1/alerts.yaml` with a contract test; - have payloads carry actions and hrefs, so Next stops hard-coding the alerts processes and tables. This blocks the strict-mode flip (qqq G2). Follow collaboration#8 and data-analysis#5. Source: Architecture review QRun-IO/qqq#1150 (docs/ARCHITECTURE-REVIEW-2026-10-13.md), finding F2.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qbit-alerts#13