feat(timeline): give deploys, payments, and alerts their own detail fields

Aperta
  • Qualcosa non va?
#400 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
nextjs, postgresql, react, typescript
Ambito
api, database, frontend

Direzione di ricerca

This is a design epic, not a patch: the plan is explicitly unspecified and the first deliverable is an options table on the issue itself. Start by reading the activity_events row in src/lib/supabase/database.types.ts, then the event details panel in src/components/timeline/event-inspector.tsx and one or two adapters under src/lib/adapters/ to see what fields each event type could emit. Compare a typed-columns migration in supabase/migrations/ against a validated jsonb payload or a side table, and check how api_activity_events is shaped today so the proposal stays non-breaking. Done means an options table with a recorded choice and sub-issues for schema, adapter, API and panel work.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: timeline enhancement epic priority: P3 size: XL

Context

Original option 8 of #377 ("Event-specific detail treatments"), split out because the #377 epic records it as its own epic, not timeline polish. The event details panel (#380) shows the same generic fields for every event: activity_events has only title, body, and url (src/lib/supabase/database.types.ts, activity_events row). Deploys, payments, and alerts would read better with fields of their own.

Plan

Not specified yet. Needs an options table before any code, covering at least:

  1. Where structured fields live (typed columns, a validated jsonb payload per event type, or a side table) and the expand-then-contract migration path.
  2. Which adapters emit them first, and how the public events API (api_activity_events) exposes them without a breaking change.
  3. The panel layout per event type. Feed rows stay consistent.

Never infer money or other facts from prose (title/body); amounts follow the money rules (integer minor units plus currency).

Acceptance criteria

  • An options table on this issue, with Eddie's choice recorded.
  • Sub-issues for the chosen schema, adapter, API, and panel work.

Files and areas

Schema (supabase/migrations/), adapters (src/lib/adapters/), public events API, src/components/timeline/event-inspector.tsx. Non-goal: changing feed rows.

Verification

Defined per sub-issue.

Model: anthropic/claude-opus-5-5 | Reasoning effort: not exposed by harness

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
6h 56m
PR unite (30g)
136

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eddiejaoude/StackDash

Tutte le issue di eddiejaoude/StackDash

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.