Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Keep diagnostic codes in one registry and check spec Appendix A against it

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend, cli, documentation, testing

Direzione di ricerca

Start with packages/engine/src/diagnostics.ts and packages/engine/src/types.ts to trace diagnostic definitions, then follow the CLI emitters in packages/cli/src/commands/check.ts and packages/cli/src/generate/verify.ts. Read docs/spec/content-pack.md Appendix A and compare its codes and severities with the registry. Done means unregistered codes are rejected, CI detects any Appendix A mismatch, and both packs retain their current lexvm check --json output.

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

Descrizione

area: cli area: engine priority: medium type: chore

Context

Diagnostic codes are a public contract: LLM repair loops, --json consumers and the documentation rely on them. Today they are string literals spread over the compiler, analyzer, verifier, play-time estimate, lexvm check (check.*) and lexvm generate (verify.*), and Appendix A of the specification is maintained by hand. Engine and CLI codes had to be aligned by hand during v0.1, and before the v0.1 pull request Appendix A was completed by diffing it against every code literal in packages/engine/src and packages/cli/src; that check cannot be repeated automatically. verify.<gate>-crashed and yaml.<code> are built from templates.

Scope

  • One registry in the engine: code, severity, stage and a one-line meaning. Emitters use typed constants; the yaml.<code> and schema.<code> families are registered as prefixes.
  • CLI codes come from the same registry.
  • A test or generator that keeps Appendix A and the registry identical (codes and severities).

Acceptance criteria

  • Emitting an unregistered code fails the typecheck or a test.
  • CI fails when Appendix A and the registry disagree.
  • No code or severity changes for existing packs: lexvm check --json output for both packs is unchanged.

References

  • packages/engine/src/diagnostics.ts
  • packages/engine/src/types.ts (Diagnostic)
  • packages/cli/src/commands/check.ts
  • packages/cli/src/generate/verify.ts
  • docs/spec/content-pack.md (Appendix A)
Lingua principale
TypeScript
Stelle
0
Fork
0
Merge medio
28m
PR unite (30g)
2

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 nullthrone/lexvm

Tutte le issue di nullthrone/lexvm

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.