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
{{ message }}
This repository was archived by the owner on Jul 15, 2023. It is now read-only.
Requirement extracted from discussion at #134 (comment). Also covered previously in #21.
I think it does make sense to go ahead with adding a Go: Install command to the extension whcih behaves similarly to the existing Go: Run tests commands.
I think it's okay for this to be fully separate from the diagnostic reporting and build-on-save.
The one place they should overlap is in reusing the go.buildFlags settings.
The big question is how to scope this. I can imagine either:
Run go install ./... in ${workspaceRoot}
Run go install in the directory of the currently opened file
For advanced uses, I'm okay with saying that folks should use VS Code Tasks. So I think this should try to cover the most common 80% for folks who don't want/need to set up the task.
Requirement extracted from discussion at #134 (comment). Also covered previously in #21.