With the extension name change from ms-vscode.Go to golang.Go, the VSCode Go extension check warns VSCode Go extension is not installed. when the extension is installed.

Adjust check to look for this extension string name rather than the previous name.

ref. The VS Code Go extension joins the Go project

It is useful for CI/CD that just wants to check the Go version.

The help text for govalidate currently is:

$ govalidate --help
Usage of govalidate:
  -ignore-cgo

  -ignore-editors

Add a nicer and more comprehensive help text.

I have VSCode Go extension installed inside WSL but the tool is not detecting it.
Go version: 1.13.5
VSCode version: 1.4.1.1
VSCode Go Extension version: 0.12.0

I tried running the program on wsl2 on windows 10 with ubuntu.

The program opens an instance of Visual studio code instead. And does not detect that the extension is installed.

On windows 10 with wsl2 enabled we can either install the vscode extensions either locally (windows 10) or remotely (ubuntu wsl2).

I tried running the command that checks for the entensions. "code --list-entensions".
On Windows Powershell it runs successfully and shows the extension that are installed locally.
On Ubuntu WSL2 it opens the instance of vscode and shows that the option is invaid.

Vim checker silently fails in numerous ways if an error occurs during the check. We don't surface any of these messages to the user. We should instead print the errors.

Otherwise, users have to reinstall a new version of govalidate to be able to see if they are using a supported Go version.

It looks like vim-go is not detected if installed via https://github.com/junegunn/vim-plug

The path checked here:

Edit: Completely unrelated to the plugin manager, actually about symlinks. Thanks for creating this tool (and your work on Go)!

https://github.com/govim/govim