This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 646
go.vetFlags does not support ${workspaceRoot} #2527
Labels
Comments
Its not difficult You see the support for $workspaceRoot for just the config flag in the lint flags. The same can be done for PRs to add this feature are most welcome.
|
thanks for the reply. I'll make a PR |
Your changes are in the latest beta version of this extension. Can you try it out and confirm that the fix works as expected? |
Thanks for the beta release. I confirmed it works as expected! |
This feature is now available in the latest update (0.11.0) to the Go extension. Thanks @tamayika! |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
I'm using custom go analyzer using https://godoc.org/golang.org/x/tools/go/analysis and https://godoc.org/golang.org/x/tools/go/analysis/unitchecker.
In command line, I can execute like below.
$ go vet -vettool=`which mytool`
I also want to use mytool in vscode-go extension, but vscode runs
go vet
in package dir, so I must set absolute path like below.However "go.vetFlags" does not support
${workspaceRoot}
, it remains as is.I found
go.lintFlags
support${workspaceRoot}
especially forconfig
flag.vscode-go/src/goLint.ts
Lines 70 to 85 in af6f7a0
Is it difficult to support this feature in vscode-go?
The text was updated successfully, but these errors were encountered: