chore(test): JavaScript and TSX have no semantic lifecycle or query cases

Aperta
#267 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à
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
62/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
testing-qa

Direzione di ricerca

Start with testdata/semantic/README.md, which sets the rule that acceptance cases are written from the source and target spec before reading CodeGraph output. Compare the existing development/ and heldout/ cases for Go, Java, Python and TypeScript with the four JavaScript and TSX cases listed in the issue. Add a lifecycle case and a public-queries case under development/, plus an acceptance-queries case under heldout/, for each of JavaScript and TSX. Done when the semantic gate runs and those new cases are picked up for both languages.

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

Descrizione

area:ci chore priority:low
What kind of chore?

Test infrastructure

What needs doing?

Add lifecycle and public query cases for JavaScript and TSX to testdata/semantic/.

Go, Java, Python and TypeScript each have a lifecycle case and a public-queries case under development/, and an acceptance-queries case under heldout/. JavaScript and TSX have two cases each, and those cases cover only the declarations and resolution dimensions:

  • development/javascript/callable-declarations
  • heldout/javascript/module-functions
  • development/tsx/components
  • heldout/tsx/nested-components

Write new acceptance cases from the source and the target specification before you look at CodeGraph output, as testdata/semantic/README.md requires.

Why now?

#264 listed this as a known limit. Without these cases, the semantic gate does not detect a lifecycle or query regression that affects only JavaScript or TSX. The other four languages have this coverage.

Does this touch anything load-bearing?
  • The release pipeline (release.yml, .goreleaser.yaml, signing)
  • The upgrade identity (internal/upgrade/verify.go)
  • The perf baseline (tools/bench/baseline.json)
  • The graph schema / meta-key layout
  • None of these
Before submitting
  • I searched existing issues and this is not a duplicate
Lingua principale
Go
Stelle
0
Fork
0
Merge medio
7h 42m
PR unite (30g)
111

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 seanb4t/codegraph-go

Tutte le issue di seanb4t/codegraph-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.