feat(web): show processing and live upload events in admin logs #953
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/admin-logs-processing"
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
Reworks Admin → Logs so media processing is actually visible and upload events are prominent + live (user request: 'ich kann nicht sehen, wenn ein Bild hochgeladen/verarbeitet wird').
GET /api/admin/job-events?churn=only&limit=100with a static 10-option type filter (never derived from the returned page), independent keyset cursor/history, and existing event formatting. Requires PR #950 (churnparam) — until that lands the feed shows its designed error state and retries on the next poll.max-h-96with internal scroll, and refreshed live via a typedrefreshUploadEventscallback wired from the page.document.hidden, refresh on visibility change, last-good data retained on transient errors, stale-response and overlapping-load guards per feed.Load olderpages and reader position survive polling (dedup by event id, newest-first tie-break) — logic extracted intojobEventFeed.tsfor unit testing.Test plan
npm run check: 0 errors (22 pre-existing warnings in unrelated files).npx vitest run: 5 files, 35 tests passed (8 new: merge/dedup/tie-break/append/unseen + churn serialization incl. legacy-omits-param).npm run build: success.admin-operator.spec.ts: desktop 6/6, mobile 6/6 (churn=only mocked separately per ISSUE-071 lesson; section-order, static filter, pagination retention, and live-refresh assertions added).Depends on: #950 (merge first). Version bump 1.21.59.