Add a dashboard flow to run and understand setup checks

Abierto
#158 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
postgresql, typescript

Línea de trabajo

Start by reading the existing dashboard patterns and the shared backend check API and result shape referenced in the issue. Trace how checks run in both Cloudflare Workers and Node/Docker deployments, then identify the dashboard entry point and relevant tests. Done means an operator can manually run checks, distinguish all result states, see next steps for failures, and the tests and listed checks pass.

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

Descripción

enhancement good first issue help wanted

Goal

Give operators a clear dashboard action to run the setup checks from #157 and understand what each result means.

What to build

  • Add a clearly named action such as Run setup checks.
  • Show each dependency as passed, failed, or unavailable.
  • Show a short explanation and a useful next step for failed checks.
  • Make it clear that PostgreSQL is checked only after the operator starts the check. Do not add background polling from the dashboard.
  • Avoid showing credentials or other secrets in the page.

Implementation guidance

Use the shared API and result shape from the backend checks. Keep the interface consistent with Codra's existing dashboard patterns. The check results must work with both Cloudflare Workers and Node/Docker deployments. If a backend change is needed for the dashboard flow, implement it for both runtimes.

Done when

  • An operator can start the checks manually and see results as they complete.
  • Passed, failed, and unavailable states are easy to distinguish.
  • Failed checks include a useful next step.
  • The page does not poll PostgreSQL or expose secrets.
  • Tests cover loading, success, failure, unavailable, and error states.
  • npm run typecheck, npm test, and npm run lint all pass.
Lenguaje dominante
TypeScript
Estrellas
125
Forks
23
Merge medio
2 d 13 h
PR fusionados (30 d)
12

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 devarshishimpi/codra

Todos los issues de devarshishimpi/codra

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.