Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

go.uselanguageserver does not work on multi-project workspaces (NodeJS) #2431

Closed
ChrisTrenkamp opened this issue Apr 9, 2019 · 4 comments
Closed
Labels
go-modules Related to Go modules upstream-gopls Issue for gopls

Comments

@ChrisTrenkamp
Copy link

ChrisTrenkamp commented Apr 9, 2019

  1. Create a Go module project in a subdirectory of your workspace
  2. Create a NodeJS project in a different subdirectory of your workspace
  3. Turn on go.uselanguageserver
  4. Autocomplete does not seem to work.

I am running VSCode 1.33.0 and am using vscode-go 0.9.3-beta.7.

A workaround is to open a workspace in the Go subdirectory of your project.

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Apr 11, 2019

Are you using multi-root workspaces? Or are both the Go and Nodejs projects are under the same ancestor and that ancestor is the folder opened in VS Code?

Do you get any error messages? Any notifications?

I am guessing you should have seen something like The Go language server is not supported in a multi root set up with different GOPATHs?

@vanackere
Copy link
Contributor

@ramya-rao-a I believe this is the same issue reported here on gopls:
golang/go#30841
See also the (duplicate) bug for more information:
golang/go#29174

@ramya-rao-a
Copy link
Contributor

Ah! Thats right, thanks @vanackere

@ChrisTrenkamp At present the language server only supports modules when they are at the root of the workspace. Please subscribe to the links @vanackere has shared above.

Closing this issue in favor of the upstream issues

@ramya-rao-a
Copy link
Contributor

fyi @stamblerre

@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
go-modules Related to Go modules upstream-gopls Issue for gopls
Projects
None yet
Development

No branches or pull requests

3 participants