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

Abierto
  • ¿Algo no está bien?
#400 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
nextjs, postgresql, react, typescript
Área
api, database, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
6 h 56 min
PR fusionados (30 d)
136

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eddiejaoude/StackDash

Todos los issues de eddiejaoude/StackDash

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.