mirror of https://github.com/golang/go.git
414ec9c3f0
The VS Code extension uses information about imports to figure out whether a given function is a Testify test. As of writing, it asks: - Does the file import Testify? - Does the package it's in do so? To answer these questions, add ListImports, which tells you about the packages imported by the current file, including their import name, plus the import paths of all imports in the entire package. I suspect the latter may be wrong in the presence of GOPATH vendoring, but that should be a relatively rare situation at this point so I didn't bother testing. Fixes golang/go#40514. Change-Id: I4c69e1db80dce6e594bdb595a81aade1ddec4d29 Reviewed-on: https://go-review.googlesource.com/c/tools/+/383354 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Robert Findley <rfindley@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> |
||
|---|---|---|
| .. | ||
| analysisinternal | ||
| apidiff | ||
| event | ||
| fakenet | ||
| fastwalk | ||
| gocommand | ||
| gopathwalk | ||
| imports | ||
| jsonrpc2 | ||
| jsonrpc2_v2 | ||
| lsp | ||
| memoize | ||
| packagesinternal | ||
| proxydir | ||
| span | ||
| stack | ||
| testenv | ||
| tool | ||
| typeparams | ||
| typesinternal | ||
| xcontext | ||