Add a dashboard flow to run and understand setup checks

Aperta
#158 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
54/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
postgresql, typescript

Direzione di ricerca

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.

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

Descrizione

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.
Lingua principale
TypeScript
Stelle
125
Fork
23
Merge medio
2g 13h
PR unite (30g)
12

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

Tutte le issue di devarshishimpi/codra

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.