Closed ronakg closed 3 years ago
I would recommend disabling the gopls
code lenses -- the gopls
code lenses are actually meant for other editors that don't have these test code lenses, and VS Code Go's are more advanced.
Duplicate of https://github.com/golang/go/issues/36787#issuecomment-648822604 We plan to utilize the info from gopls if the issue is resolved - still we will need to replace the code lens's commands with the extension's implementation.
Please answer these questions before submitting your issue. Thanks!
What version of Go, VS Code & VS Code Go extension are you using?
go version
to get version of Go from the VS Code integrated terminal.go version go1.15.7 darwin/amd64
gopls -v version
to get version of Gopls from the VS Code integrated terminal.code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.0.22.0
Go: Locate Configured Go Tools
command.Share the Go related settings you have added/edited
Describe the bug
I have disabled the extension's test codelens and have enabled gopls' test codelens. The gopls' version of test codelens does not generate the package/file level code lenses.
Example of extension's version of test codelens at the top of the file:
This is missing when enabling gopls' version of test codelens.