tailscale / tailscale/depaware
consider showing test-only dependencies
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 459
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
The ability to more easily see what are test-only dependencies for modules is a common request for cmd/go.
Consider supporting it here, either by highlighting a test-only dependency or by highlighting a non-test dependency.
There are different ways to determine this, but one way is this, which shows the modules used in your build excluding test-only dependencies:
go list -deps -f '{{with .Module}}{{.Path}} {{.Version}}{{end}}' ./... | sort -u
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files or tests are named. Start by comparing depaware's current dependency output with the provided go list -deps -f ... ./... | sort -u command, then determine how test-only dependencies should be identified and displayed. Done means the tool clearly distinguishes test-only from non-test dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100