|author||Heschi Kreinick <email@example.com>||Mon Sep 14 18:31:33 2020 -0400|
|committer||Heschi Kreinick <firstname.lastname@example.org>||Tue Sep 15 17:38:23 2020 +0000|
internal/lsp/cache: fix -mod=mod for workspace module setups When we're in workspace module mode, there may not be a go.mod at the root of the workspace, so checking modURI != "" doesn't tell us whether module mode is on. Add a flag to workspaceMode which is exactly that. There are probably many more places that should be updated, but since the design is in flux I don't want to cause more churn than necessary. This is enough to unblock -mod=readonly by default. (I missed this in CL 253799 because I was running the wrong Go Version.) Change-Id: I718ee44c7a2547c90f9d62393aba390c9b4b0f46 Reviewed-on: https://go-review.googlesource.com/c/tools/+/254756 Trust: Heschi Kreinick <email@example.com> Run-TryBot: Heschi Kreinick <firstname.lastname@example.org> TryBot-Result: Go Bot <email@example.com> Reviewed-by: Rebecca Stambler <firstname.lastname@example.org>
This subrepository holds the source for various packages and tools that support the Go programming language.
Some of the tools,
vet for example, are included in binary Go distributions.
Others, including the Go
guru and the test coverage tool, can be fetched with
Packages include a type-checker for Go and an implementation of the Static Single Assignment form (SSA) representation for Go programs.
The easiest way to install is to run
go get -u golang.org/x/tools/.... You can also manually git clone the repository to
This repository uses prettier to format JS and CSS files.
The version of
prettier used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the tools repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/tools/(your subdir):” in the subject line, so it is easy to find.