commit | 7d467dcfbb94234d0e09a32fb034c63ad0d8b8dd | [log] [tgz] |
---|---|---|
author | Rebecca Stambler <rstambler@golang.org> | Thu Aug 12 16:49:51 2021 -0400 |
committer | Rebecca Stambler <rstambler@golang.org> | Wed Sep 29 19:20:39 2021 +0000 |
tree | d1d7082490ae2290ceceed2377fe2db2fafefcf8 | |
parent | d9648c9910403d717325881aa6d3b919d42fc7a7 [diff] |
internal/lsp: support go.work outside of experimental This change handles the case of the user creating a go.work file during the gopls session. It also defaults to go.work/gopls.mod being used outside of experimental mode, so that you don't have to both set a setting and have a file. Change-Id: If118cd2fc95c1b5600a6c06217a3b61605b11e28 Reviewed-on: https://go-review.googlesource.com/c/tools/+/342170 Trust: Rebecca Stambler <rstambler@golang.org> Run-TryBot: Rebecca Stambler <rstambler@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com>
This subrepository holds the source for various packages and tools that support the Go programming language.
Some of the tools, godoc
and vet
for example, are included in binary Go distributions.
Others, including the Go guru
and the test coverage tool, can be fetched with go get
.
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 $GOPATH/src/golang.org/x/tools
.
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.