MechaCat02 529d34af83 feat(v1.1.9): dashboard Queues tab + queue:receive trigger form + 0.15.0 ...

API client (src/lib/api.ts):
- TriggerKind gains 'queue'
- TriggerDetails gains { kind: 'queue', queue_name, visibility_timeout_secs, last_fired_at }
- CreateQueueTriggerInput, QueueSummary, QueueConsumer, QueueDetail
- api.triggers.createQueue(idOrSlug, input) -> POST /admin/.../triggers/queue
- api.queues.list(idOrSlug) -> GET /admin/.../queues
- api.queues.get(idOrSlug, name) -> GET /admin/.../queues/{name}

New routes:
- /apps/[slug]/queues — read-only list view (queue_name, total, pending,
  claimed, drilldown link); empty state explains how queues are created
  (first enqueue) and that consumers register via the Triggers tab
- /apps/[slug]/queues/[name] — drilldown showing depth + registered
  consumer (script name + visibility timeout + last_fired_at + trigger
  id); empty consumer state surfaces clearly

App detail page (src/routes/apps/[slug]/+page.svelte):
- New "Queues" link in the app-level nav between Files and Dead letters
- Triggers tab gains a "Queue:receive trigger (v1.1.9)" form alongside
  cron/pubsub/email — target script select, queue_name, visibility
  timeout (5–3600s, default 30), max_attempts (1–20, default 3)
- Trigger list renders queue triggers with queue_name + visibility
  timeout + last_fired_at

dashboard/package.json: 0.14.0 -> 0.15.0

npm run check — all queue/invoke-related code typechecks clean; the
existing Playwright test errors (149 unrelated) carry forward unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-06-06 22:41:59 +02:00

1.5 KiB

Raw Blame History

View Raw