Add a dashboard flow to run and understand setup checks

Offen
#158 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
54/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
postgresql, typescript

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
TypeScript
Sterne
125
Forks
23
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus devarshishimpi/codra

Alle Issues in devarshishimpi/codra

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.