| commit | a0016a2adeac320313ad5952f94282afebee9a9f | [log] [tgz] |
|---|---|---|
| author | pjw <pjw@google.com> | Fri Sep 17 15:39:32 2021 -0400 |
| committer | Peter Weinberger <pjw@google.com> | Mon Sep 20 15:08:51 2021 +0000 |
| tree | 0366e2ca983f0461b36d372b320b287180fceb0f | |
| parent | 7559231edc438c5cdc12c97198b1e202348b651e [diff] |
internal/lsp/diagnostics: avoid erroneous error message for orphaned files If the user changes the extension of a go file while editing, the existing code complains 'No packages found for open file'. This error messsag is not helpful and this CL avoids it. Change-Id: Idf426f1ce8b83b23757f81aa1f322fea86df9d82 Reviewed-on: https://go-review.googlesource.com/c/tools/+/350789 Run-TryBot: Peter Weinberger <pjw@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Peter Weinberger <pjw@google.com> 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.