Recently, I have written a module lbry/cli in Go. I have hosted that module here: https://github.com/lbryfoundation/lbry-cli, but we may host it on other Git location in the future too. When people want to use this package, I expect them to do this in their go.mod file:
replace lbry/cli => github.com/lbryfoundation/lbry-cli master
However, Go Report Card doesn't seem to handle this situation. When I only enter lbry/cli, it doesn't know where this package is, so it tries https://proxy.golang.org/lbry/cli/@latest, fails, and shows this error:
There was an error processing your request: Could not analyze the repository: could not download repo: could not get latest module version from https://proxy.golang.org/lbry/cli/@latest
When I enter github.com/lbryfoundation/lbry-cli, it will see that the module name is lbry/cli and, instead of using github.com/lbryfoundation/lbry-cli, it again uses lbry/cli and fails again.
To fix this error, the tool should be made a little bit smarter, or there should be added an advanced option to enter a replace directive too.
Recently, I have written a module
lbry/cliin Go. I have hosted that module here: https://github.com/lbryfoundation/lbry-cli, but we may host it on other Git location in the future too. When people want to use this package, I expect them to do this in theirgo.modfile:However, Go Report Card doesn't seem to handle this situation. When I only enter
lbry/cli, it doesn't know where this package is, so it tries https://proxy.golang.org/lbry/cli/@latest, fails, and shows this error:When I enter
github.com/lbryfoundation/lbry-cli, it will see that the module name islbry/cliand, instead of usinggithub.com/lbryfoundation/lbry-cli, it again useslbry/cliand fails again.To fix this error, the tool should be made a little bit smarter, or there should be added an advanced option to enter a replace directive too.