Support go.work workspaces
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, typescript
- Domain
- build-system
Research direction
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.
Written by the indexing model from the issue text.
Description
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.workexists and everyusedirectory is inside the repository, rungo list -deps -test -jsonfor each workspace module (or once withGOWORKon, 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 testfrom the right module directory, with one command group per module if needed.
Must fall back (blocker)
- A
usedirectory outside the repository, areplaceingo.workpointing outside it, orgo listfailing for any module. - Changes to
go.workorgo.work.sum(already a full run through the configuration-change rule).
Done when
- A fixture with
go.workand two modules, wherebimportsa, shows that a change inaselects tests in both modules and a change inbselects onlyb.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 4
- Avg merge
- 18h 41m
- Merged PRs (30d)
- 48
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DiffCI/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at randomPossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Agent tools: changed_files lists only the new path of a renamed filePossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
adapter good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·