commit | a3d3b81f107cbeb2587d7b6eac6b46a1c69e4f48 | [log] [tgz] |
---|---|---|
author | Hana <hyangah@gmail.com> | Wed Mar 02 13:52:07 2022 -0500 |
committer | Hana <hyangah@gmail.com> | Wed Mar 02 13:52:07 2022 -0500 |
tree | 54db56b5dd524847747576fbc14399c89ac7a2a3 | |
parent | 44e78e90570ed554f42a30ad45751dc57ae8a588 [diff] | |
parent | 03af3d4771f34b31888476f59207272eea1106df [diff] |
[release] prepare v0.32.0 03af3d4 package.json: sync gopls settings @ v0.8.0 1274335 package.json: fix spelling for generateTestForPackage b6187d8 package.json: add go.toolsManagement.go 6399238 codereview.cfg: declare issue repo 09c4936 src/goEnv.ts: pass uri to getGoConfig 0f849d1 src/config: add ExtensionInfo to replace isInPreview/isInCloudIDE 0bd09b6 src/goMain: install tools for suggested updates if autoUpdate is on 2434bfa src/utils: add utils/README.md and move test_events.md to goTest acbe503 src/goImport,goOutline: check registered gopls commands 4aa4554 src/goLanguageServer: skip buildLanguageClient if it's disabled 073b8fc src/goLanguageServer: include go version in the gopls crash report e6dc469 src/goLanguageServer: sample half of gopls opt-out users for survey 4b6318c src/goLanguageServer: clean unused `surveyOnly` param 5494d35 src/goLanguageServer.ts: don't let config change trigger opt-out survey 2222461 src/goOutline.ts: use regexp to find package decl 7bc14ec src/goStatus: add go.work to status bar quickpick 16eadfa src/goMain: suggest tool updates if tools were compiled with old go 934911a src/goLanguageServer: cache language server info 28136c8 src/goOutline: use language server to get document symbols af9afa3 src/goMain.ts: remove warning about dlv-dap in alternateTools bdcd7a6 src/goMain.ts: remove prompt for nightly extension users b3048fc src/goLanguageServer: use 1.42+ workspace.getConfiguration API 9156fb4 src/goMain: use inspectGoToolVersion instead of runGoVersionM 3e9fb0e src/util: remove vendoring support check 4435e8e src/util: fix vendor support check 37ffd3c test: update switch goroutine test e04eb10 build: log shm size & increase shm size to 8G e50cf23 src/goPackages: make goListPkgs async and run go list with -e 5b290fa CHANGELOG.md: list changes for v0.31.1 fb8ba52 vscode-go: remove references to gopkgs 68fae93 tools: remove gopkgs from all tools information 037e8a3 src/goTest: avoid a name conflicting with the proposed quickpick api 3ad379c src/goEnvironmentStatus: use installTool for golang.org/dl/* install 9d0ec81 .github/workflows: replace go1.18-beta1 with go1.18-beta2 c01699e docs/features.md: discuss default formatting behavior and template support c5ebe02 docs/advanced.md: use go1.18beta2 in the instruction d5403b9 src/goToolsInformation: require go1.13+ for gopls 0a9d740 .github/workflows: partially revert go.dev/cl/380175 59d4c16 test/integration: skip 'disconnect with multiple disconnectRequests' test 92797b2 package.json: bump dev version to 0.32.0 6264294 docs/advanced.md: fix broken link and add more links debf84a docs/advanced.md: add go1.18 instruction 2735f15 src/goTest: remove '#' in subtest name parsing cutset c42b3cd src/goTest: detect Fuzz tests and list them in test explorer UI 6a37048 workflows: replace repository dispatch with workflow dispatch b5b4835 CHANGELOG.md: Update changelog for release continued 6135b6e src/goPackages.ts: replace use of gopkgs with go list 1b607ad tests/testdata: fix package name in importTest 6fb2a2a package.json: update mocha@v9.2.0 e4e5dfa test: remove flaky step out test 59db2c8 tools/license.sh: only include production dependencies in LICENSE Change-Id: Ia9e1dab191444b17f968ba64c9e95556ac5483ee
The VS Code Go extension provides rich language support for the Go programming language.
📣 Remote attach debugging is now available via Delve's native DAP implementation with Delve v1.7.3 or newer. We plan to enable this as the default in early 2022 to enhance remote debugging with the same debugging features that are already in use for local debugging. We recommend switching your remote attach configurations in launch.json
to use "debugAdapter":"dlv-dap"
now to verify that this works for you. Please file a new issue if you encounter any problems.
📣📣 Watch Debugging Treasure Hunt from GopherCon 2021 for a fun take on a debugging demo with VS Code Go and Delve DAP.
Welcome! 👋🏻
Whether you are new to Go or an experienced Go developer, we hope this extension fits your needs and enhances your development experience.
You are ready to Go :-) 🎉🎉🎉
Please be sure to learn more about the many features of this extension, as well as how to customize them. Take a look at Troubleshooting and Help for further guidance.
If you are new to Go, this article provides the overview on Go code organization and basic go
commands. Watch “Getting started with VS Code Go” for an explanation of how to build your first Go application using VS Code Go.
This extension provides many features, including IntelliSense, code navigation, and code editing support. It also shows diagnostics as you work and provides enhanced support for testing and debugging your programs. See the full feature breakdown for more details and to learn how to tune its behavior.
In addition to integrated editing features, the extension provides several commands for working with Go files. You can access any of these by opening the Command Palette (Ctrl+Shift+P
on Linux/Windows and Cmd+Shift+P
on Mac), and then typing in the command name. See the full list of commands provided by this extension.
⚠️ Note: the default syntax highlighting for Go files is provided by a TextMate rule embedded in VS Code, not by this extension.
The extension uses a few command-line tools developed by the Go community. In particular, go
, gopls
, and dlv
must be installed for this extension to work correctly. See the tools documentation for a complete list of tools the extension depends on.
In order to locate these command-line tools, the extension searches GOPATH/bin
and directories specified in the PATH
environment variable (or Path
on Windows) with which the VS Code process has started. If the tools are not found, the extension will prompt you to install the missing tools and show the “⚠️ Analysis Tools Missing” warning in the bottom right corner. Please install them by responding to the warning notification, or by manually running the Go: Install/Update Tools
command.
Go modules are how Go manages dependencies in recent versions of Go. Modules replace the GOPATH
-based approach to specifying which source files are used in a given build, and they are the default build mode in go1.16+. While this extension continues to support both Go modules and GOPATH
modes, we highly recommend Go development in module mode. If you are working on existing projects, please consider migrating to modules.
Unlike the traditional GOPATH
mode, module mode does not require the workspace to be located under GOPATH
nor to use a specific structure. A module is defined by a directory tree of Go source files with a go.mod
file in the tree's root directory.
Your project may involve one or more modules. If you are working with multiple modules or uncommon project layouts, you will need to configure your workspace by using Workspace Folders. Please see this documentation about supported workspace layouts.
The extension needs no configuration and should work out of the box. However, you may wish to adjust settings to customize its behavior. Please see the settings documentation for a comprehensive list of settings. See advanced topics for further customizations and unique use cases.
If the extension isn't working as you expect, you can take a look at our troubleshooting guides. There is one for general troubleshooting, and another specifically for troubleshooting the debugging feature.
If the troubleshooting guides did not resolve the issue, please reach out to us by filing an issue, starting a GitHub discussion, or by asking a question on Stack Overflow.
Also, you can take a look at go.dev/learn and golang.org/help for more general guidance on using Go.
If you'd like to get early access to new features and bug fixes, you can use the nightly build of this extension. Learn how to install it in by reading the Go Nightly documentation.
We welcome your contributions and thank you for working to improve the Go development experience in VS Code. If you would like to help work on the VS Code Go extension, please see our contribution guide. It explains how to build and run the extension locally, and describes the process of sending a contribution.
This project follows the Go Community Code of Conduct. If you encounter a conduct-related issue, please mail conduct@golang.org.