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

未关闭
#267 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
62/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
领域
testing-qa

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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
主要语言
Go
星标
0
派生
0
平均合并
7 小时 42 分钟
30 天内合并 PR
111

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

seanb4t/codegraph-go 的其他 Issue

查看 seanb4t/codegraph-go 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。