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
What version of Go, VS Code & VS Code Go extension are you using?
Version Information
Run go version to get version of Go from the VS Code integrated terminal.
go version go1.22.2 linux/amd64
Run gopls -v version to get version of Gopls from the VS Code integrated terminal.
golang.org/x/tools/gopls v0.16.2
Run code -v or code-insiders -v to get version of VS Code or VS Code Insiders.
1.95.3
Check your installed extensions to get the version of the VS Code Go extension
v0.42.1
Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools command.
Share the Go related settings you have added/edited
Run Preferences: Open Settings (JSON) command to open your settings.json file.
Share all the settings with the go. or ["go"] or gopls prefixes.
Describe the bug
Coverage is only rendered on real paths, not soft link paths.
It seems to be a problem that has been around for a long time. I would like to ask if it has not been dealt with or if there is any consideration.
I think it should also be necessary to support the rendering of symbolic link paths?
Steps to reproduce the behavior:
just create a simple code with xx_test.go
and create this folder symbolic link
then open symbolic link folder in vscode
toggle to show go-cover
Screenshots or recordings
It seems to be a problem that has been around for a long time. I would like to ask if it has not been dealt with or if there is any consideration. #1803
Symbolic links are notoriously hard to deal with, as it requires every tool in a chain to preserve them. With that said, I hope that we can avoid this bug.
What version of Go, VS Code & VS Code Go extension are you using?
Version Information
go version
to get version of Go from the VS Code integrated terminal.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.Go: Locate Configured Go Tools
command.Share the Go related settings you have added/edited
Run
Preferences: Open Settings (JSON)
command to open your settings.json file.Share all the settings with the
go.
or["go"]
orgopls
prefixes.Describe the bug
Coverage is only rendered on real paths, not soft link paths.
It seems to be a problem that has been around for a long time. I would like to ask if it has not been dealt with or if there is any consideration.
I think it should also be necessary to support the rendering of symbolic link paths?
Steps to reproduce the behavior:
Screenshots or recordings
It seems to be a problem that has been around for a long time. I would like to ask if it has not been dealt with or if there is any consideration.
#1803
I had see in here to say that's a actual path: https://github.com/golang/vscode-go/blob/master/extension/src/goCover.ts#L231
so why can't use symbolic link path to render
The text was updated successfully, but these errors were encountered: