justfile does not specify path of yardl so can use the wrong version

[KrisThielemans]

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!

[naegelejd]

This is why we highly recommend developing Yardl using a devcontainer - currently the only development environment we have the bandwidth to support.

But even if you really want to develop it locally, the behavior you describe is as expected. Using go requires setting $GOPATH, and running go install installs your binaries to that directory.

We could parameterize the full path to Yardl to support your use case, but it really just comes down to the order of items on your $PATH, which you fully control on your machine.

[KrisThielemans]

fair enough. Maybe we could just update the installation instructions a little bit. I can draft something later, if you point me to the best place.