| commit | 5d3b3f65d2f08ab95de3223bd347026cdcf82a2a | [log] [tgz] |
|---|---|---|
| author | Hana <hyangah@gmail.com> | Tue Sep 14 14:02:49 2021 -0400 |
| committer | Hana <hyangah@gmail.com> | Tue Sep 14 14:06:36 2021 -0400 |
| tree | 74dcf1f3765fc601f27578347cf215a27d3252ae | |
| parent | 5d22417d2b3110c8f8a0617b7f573068b15754f6 [diff] | |
| parent | c0e33de4263469e1c6bc25b4723ca19212ea4682 [diff] |
[release] prepare v0.28.0 release c0e33de src/goEnvironmentStatus: update hard coded go versions 81f6db9 src/goModules: update example module names to reflect naming guidelines ba2daa3 src/goMain.ts: disable check for active debug session d32a326 package.json: drop minify when packaging cc6f312 src/debugAdapter: let infer path logic handle non-existing files 5a59bbf src/goDebugConfiguration: remote attach should not be warned about port 1d258a2 src/goTest: group test explorer settings, fix bugs 104052d package.json: update gopls settings (v0.7.2) dc044d1 test/integration: write legacy DA trace line-by-line 3a09d5d test/integration: log DAP trace when legacy adapter test fails 9248382 src/config: remove WrappedConfiguration in favor of trusted workspace fb6208d docs: change blog.golang.org to go.dev/blog ab3d3a6 src/goDebugFactory: add --check-go-version=false 9a9ec9a src/goTest: cleanup b9bf001 src/goTest: basic profiling support 850fefd test/integration/goTest: remove unused imports d1d9901 src/goTest: fix test run cancellation 977e93e docs/debugging.md: add FAQ section for next while nexting 6019957 src/goTest: support running sub-tests 9021bff src/goTest: do not set range for dynamic subtests 1c36262 src/goDebugConfiguration: show warning that port is being used 09d4bbe docs/debugging.md: update description of port and host 41279a6 Revert "src/goDebugFactory.ts: direct users to use 'debugServer' for remote" a4c2c4a CHANGELOG.md: prep for v0.27.2 53accf5 src/goDebugFactory: fix debugger launch on Windows e6c2d3c all: change learn.go.dev to go.dev/learn aa3293c src/goDebugConfiguration: massage launch config for debug/test 289839c test/integration/goDebug.test.ts: enable disconnect tests c069def src/goTest: remove unused names e53d60e src/goTest: clean up test ID parsing 3e12e73 src/goTest: split up test explorer a1cc5e5 src/goInstallTools: unpin dlv-dap version, and pick master 2ff7ead src/goTestExplorer: handle stretchr suites 33d814a .github: update issue template to collapse version details ebd07b1 src/goDebugConfiguration+docs: improve dlvLoadConfig communication c3de634 codelens: fix regexps for test funcs names 2f484bd src/goTestExplorer: handle weird doc URIs on load c79e0c4 src/goDebugFactory: increase timeout for dlv dap server start 3f434bd all: bundle with esbuild instead of webpack 83aa2cb src/goTestExplorer: implement a test provider for the new test api 945a47e package.json: recognize *.*tmpl as go template files ad3a6ca all: add support for go.work files as go.mod files 0ff533d tools/relnotes: use types from work-stats package e81d5fc CHANGELOG.md: v0.27.1 change log 46b3efe src/goToolsInformation: use the commit hash to pin dlv-dap version e0a268b package-lock.json: npm audit fix 336b9f7 src/goDebugConfiguration: convert processId to int b4226ab package.json: add support for replay and core debug modes 6060589 docs/debugging.md: add FAQ section 6a6fdb6 src/goDebugFactory: log errors without killing delve process 4e7f6f5 src/goMain: export a small API 8a4731f package.json: start v0.28.0-dev cd72252 package.json: use fileDirname for Launch Package snippet f77de39 CHANGELOG.md: mention the removal of 'port' support in dlv-dap 45b06e0 src/goDebugFactory.ts: direct users to use 'debugServer' for remote Updates golang/vscode-go#1776 Change-Id: Ifd897cf869e1f1a485026d0631b88b00d2ec83ce
The VS Code Go extension provides rich language support for the Go programming language.
📣 Debugging using
Delve's native DAP implementation is enabled by default in v0.27.0.
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.