CodeLens references do not work in module mode if it is in another file

[karim]

What version of Go, VS Code & VS Code Go extension are you using?

• Run go version to get version of Go
  • go version go1.13.6 windows/amd64
• Run code -v or code-insiders -v to get version of VS Code or VS Code Insiders
  • 1.41.1 26076a4de974ead31f97692a0d32f90d735645c0 x64
• Check your installed extensions to get the version of the VS Code Go extension
  • 0.12.0
• Run go env GOOS GOARCH to get the operating system and processor arhcitecture details
  • windows amd64

Share the Go related settings you have added/edited

"go.useLanguageServer": true,
"go.languageServerExperimentalFeatures": {
    "documentLink": false,
},
"gopls": {
    "completeUnimported": true,
    "hoverKind": "FullDocumentation",
    "staticcheck": true,
},
"go.enableCodeLens": {
    "references": true,
    "runtest": true
}

Describe the bug

Showing references does not work in module mode if they are in different files.

However, if I moved the function to the same file it works.

Or if I moved the whole project inside GOPATH.

[stamblerre]

This is probably because the references codelens relies on the default references provider, which I would guess doesn't work with modules (see here). We should be able to get the references provider from the language server if it's in use. Does that sound right to you, @ramya-rao-a?

[ramya-rao-a]

The catch is in figuring out if the extension can call the reference provider from the language server.
Am not sure if that is possible..

I would suggest that we start looking into the language server it self implementing the code lens

[stamblerre]

That sounds reasonable. Filed golang/go#36787 to track this upstream.

[ramya-rao-a]

Thanks @stamblerre

@karim Closing this issue in favor of the upstream issue logged above.
There is no further work in guru to fix references in module mode, so we will need to wait for gopls, the language server to support this.