canonical / canonical/source-wand
Need to consider `replace` in go.mod files
Open
Nobody has claimed this yet.
go
- Dominant language
- Rust
- Stars
- 9
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I don't think we currently consider what is going on in replace when we build out our dependency tree.
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
Start by locating the dependency-tree construction and the code that reads go.mod files; no specific files or tests are named in the issue. Trace how module requirements are represented, then determine how replace directives should affect the tree and add coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100