[release] prepare v0.25.0 release

c7fcd42 .github/workflows: change tabs to spaces
f5ef2de .github/workflows: install stable delve version for testing
c522170 test/integration/goDebug.test.ts: fix listening for output event
ad0e420 src/goDebugFactory: log console message with info level
07fe3d3 src/goDebugFactory: disable logDest support on windows
a7f91bb src/goTools: update dlv-dap version
4e3fc58 src/goMain: overwrite process.env[GOROOT] if go.goroot is set
730d202 test/integration/goDebug: make logDest file less flaky
a73da23 test/integration/goDebug: output trace for dlv dap cleanup test
c807011 Revert "Revert "src/goDebugFactory: use --log-dest to capture dlv logs and add logDest""
7bfa543 src/goLanguageServer: disable the language features for unrecognized workspace types
a031e96 src/goDebugConfiguration.ts: use `program` to determine mode if file
9005b0c package.json: recognize 'stopOnEntry' in attach mode
8fa9dbd src/goDebugConfiguration.ts: disable warning about using 'cwd' in dap
cdbf062 goLanguageServer: only prompt for the survey when working on Go code
5f1faa3 goSurvey: pull survey logic out of goLanguageServer.ts
b1cb6c5 src/util: adjust go dev version regex
ae07a73 test/integration/goDebug.test.ts: set 'output' for tests
bdd4acd src/goLanguageServer: prompt for the survey regardless of gopls usage
e3bcd86 src/goDebugFactory: send SIGINT to delve and avoid treekill
acc65d3 src/goDebugConfiguration.ts: show warning for dlv-dap with dlvLoadConfig
7a1a338 test/integration/goDebug: don't wait for debug client to stop in teardown
4463476 test/integration/goDebug: get goroutines reliably in switch goroutine test
57ba505 debugAdapter: fix missing file bug for remote debugging
c5ca0dc test/integration/goDebug: skip more remote attach tests
a496b7a test/integration/goDebug: skip remote attach tests
78b5f53 test/integration/goDebug: verify goroutines running before switch
5e9eef4 Revert "src/goDebugFactory: use --log-dest to capture dlv logs and add logDest"
71410c4 src/goDebugFactory: use --log-dest to capture dlv logs and add logDest
b2f6fcf test/integration: disable broken setSelectedGo test
64ad2e0 src/goDebugFactory: start dlv dap process early
2e81d29 .github: stop sending feature requests to discussions/slacks
2875e05 package.json: add command to run 'go mod init'
5bcfcac test/integration/goDebug: set mode to 'debug' or 'test' not 'auto'
9bc6048 test/integration/goDebug.ts: check for incorrect output event noDebug
b7797c3 src/goDebugConfiguration.ts: replace resolvePath with resolveHomeDir
ec08530 src/debugAdapter: accept additional trace levels
5639184 src/welcome: avoid vscode.Uri.joinPath
aabfc9f src/goTools: update dlv-dap @v1.6.1-0.20210419181450-2408ed87bf87
5efb087 test/integration/statusbar: fix/delete broken tests
e0e1e60 src/goDebugFactory: send teardown log to Go Debug channel
cfc787e src/goDebugFactory: add GoDebugAdapterTrackerFactory
8755d84 src/goLogging: extend logging facility
afa59f6 src/goTest.ts: add debug previous command
015d002 src/goInstallTools: use GOBIN correctly installing dlv-dap/gocode-gomod
10509fb src/goCheck: add missing goplsConfig parameter to goLint
4b6f857 package.json: set editor.suggest.snippetsPreventQuickSuggestions to false
a9b31d9 [release] Update CHANGELOG and LICENSE for v0.24.1
86f704a src/goDebugConfiguration: auto update dlv-dap if autoUpdates enabled
bd55732 src/goDebugFactory.ts: send the first error when starting dlv-dap
f607db9 test/runTest: stop creating ${workspaceFolder} directory

Change-Id: I89fc378ea4a30900fc3bda5fc11aedc6bcff71f4
tree: fe5b107df0c80eaf0fa46347293f9ca39df218c7
  1. .github/
  2. .vscode/
  3. build/
  4. docs/
  5. languages/
  6. media/
  7. snippets/
  8. src/
  9. syntaxes/
  10. test/
  11. third_party/
  12. tools/
  13. typings/
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.json
  17. .gitignore
  18. .prettierrc.js
  19. .prettierrc.json
  20. .vscodeignore
  21. CHANGELOG.md
  22. CODE_OF_CONDUCT.md
  23. go.mod
  24. LICENSE
  25. package-lock.json
  26. package.json
  27. README.md
  28. SECURITY.md
  29. tsconfig.json
  30. webpack.config.js
README.md

Go for Visual Studio Code

Slack

The VS Code Go extension provides rich language support for the Go programming language.

📣 Gopls, the official Go language server, is now enabled in VS Code by default. Gopls replaces several legacy tools to provide IDE features while editing Go code. See issue 1037 for more information.

Quick Start

Welcome! 👋🏻
Whether you are new to Go or an experienced Go developer, we hope this extension fits your needs and enhances your development experience.

  • Step 1. If you haven't done so already, install Go and the VS Code Go extension.
  • Step 2. To activate the extension, open any directory or workspace containing Go code. Once activated, the Go status bar will appear in the bottom left corner of the window and show the recognized Go version.
  • Step 3. The extension depends on a set of extra command-line tools. If they are missing, the extension will show the “⚠️ Analysis Tools Missing” warning. Click the notification to complete the installation.

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.

Features

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.

Tools

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.

Setting up your workspace

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.

Customization

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.

Troubleshooting

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.

Ask for help

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 in the Gophers Slack. We hang out in the #vscode channel!

Also, you can take a look at learn.go.dev and golang.org/help for more general guidance on using Go.

Preview version

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.

Contributing

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.

Code of Conduct

This project follows the Go Community Code of Conduct. If you encounter a conduct-related issue, please mail conduct@golang.org.

License

MIT