justfile does not specify path of yardl so can use the wrong version
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 35
- Forks
- 14
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
There seems to be no PATH information. In my case, (not using the devcontainer, but just ubuntu) just install installed yardl in $HOME/go/bin (which is the default for go), which was not in my PATH. I did not even notice this, because the rest of the justfile was then picking up an (old) yardl version somewhere else in my PATH.
Lots of scope for confusion!
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 reading the repository's justfile, especially the install recipe and the commands that invoke yardl. Reproduce the behavior on Ubuntu without the devcontainer, checking the installed yardl location and the version selected from PATH. Done means the justfile consistently uses the intended yardl installation rather than an older executable elsewhere in PATH.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100