Support go.work workspaces

未關閉
#79 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
30/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
go, typescript
領域
build-system

研究方向

Start with the Go adapter, where go list is run with GOWORK=off and where the single-root go.mod fallback message is raised, and with the test command that does the same. The issue asks for a fixture with go.work and two modules, where b imports a, to show that a change in a selects tests in both modules while a change in b selects only b. Done means that fixture passes and the fallback still triggers for go.work edits and for use or replace paths outside the repository.

由索引模型根據 Issue 內容生成。

描述

adapter enhancement help wanted

Part of #76.

Any repository with a go.work file falls back today:

Go support requires one root go.mod; workspaces and nested modules require full validation

The adapter runs go list with GOWORK=off, and the test command does the same.

Proposal

  • When go.work exists and every use directory is inside the repository, run go list -deps -test -json for each workspace module (or once with GOWORK on, if offline listing stays reliable) and merge the packages into one graph. Cross-module imports between workspace modules become normal package edges.
  • Map each test file to its module and package, and run go test from the right module directory, with one command group per module if needed.

Must fall back (blocker)

  • A use directory outside the repository, a replace in go.work pointing outside it, or go list failing for any module.
  • Changes to go.work or go.work.sum (already a full run through the configuration-change rule).

Done when

  • A fixture with go.work and two modules, where b imports a, shows that a change in a selects tests in both modules and a change in b selects only b.
主要語言
TypeScript
星號
0
分支
4
平均合併
18 小時 41 分鐘
30 天內合併 PR
48

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

DiffCI/core 的其他 Issue

查看 DiffCI/core 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。