x/tools/gopls: gopls not detecting embedded projects

[kkrime]

Go version

gopls v0.17.1

Output of go env in your module/workspace:

GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/kkrime/Library/Caches/go-build'
GOENV='/Users/kkrime/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/kkrime/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/kkrime/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/kkrime/go/pkg/mod/golang.org/[email protected]'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/kkrime/go/pkg/mod/golang.org/[email protected]/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.3'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/Users/kkrime/go/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/c3/rzmnfcrn17g80qs3g6pj43xr0000gn/T/go-build3355237921=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?

If we have the following:
outter_project: /User/kkrime/go/src/outter_project
inner_project: /User/kkrime/go/src/outter_project/inner_project

Both projects are vaild go projects with all the files you'd expect in the root of a golang project folder

What did you see happen?

If you open the outter_project first then open the inner_project, then gopls will only return the outter_project as a workspace_folder

nvim outta_project/main.go outter_project/innner_project/main.go -O

If you do it the other way round i.e first open the inner_project then open the outter_project, gopls will return both projects workspace_folder

nvim outter_project/innner_project/main.go outta_project/main.go -O

What did you expect to see?

gopls should return both projects workspace_folders in both senarios

[gabyhelp]

Related Issues

• x/tools/gopls: expands workspace to the wrong root when go.mod file is above go.work. #63917 (closed)
• x/tools/gopls: go modules in subfolders of VSCode folder are not recognized #37838 (closed)
• x/tools/gopls: defining the workspace root #36899 (closed)

Related Discussions

• Need Help: gopls and VSCode Setup with the Go Project - Nested Module Error

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[findleyr]

Hi @kkrime, gopls does not return workspace folders: those are provided by the LSP client. Which nvim client are you using?

FWIW, I use coc.nvim, and frequently work in the x/tools and x/tools/gopls modules. I use a go.work file to unify the two modules into a single workspace.

Nevertheless, if you open a file in inner_project, gopls should automatically detect the distinct build configuration, and work correctly in the inner module. But it won't consider the module part of the workspace until you open a file in it.

Closing as (AFAICT) this is a client issue. Please comment if I'm misunderstanding.