You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we locate the go.mod file using methods like go env GOMOD, which we consider a clever approach. However, it is not completely accurate. In some special cases, go build might execute outside of the user's source code, and in such scenarios, we might end up finding the incorrect go.mod file and consequently retrieve the wrong module name. I believe we should reference the Golang build process code and specifically use code similar to the following to search for go.mod
Currently, we locate the go.mod file using methods like go env GOMOD, which we consider a clever approach. However, it is not completely accurate. In some special cases, go build might execute outside of the user's source code, and in such scenarios, we might end up finding the incorrect go.mod file and consequently retrieve the wrong module name. I believe we should reference the Golang build process code and specifically use code similar to the following to search for go.mod
https://github.com/golang/go/blob/485ed2fa5b5e0b7067ef72a0f4bdc9ca12b77ed7/src/cmd/go/internal/modload/init.go#L1598
The text was updated successfully, but these errors were encountered: