Release 0.19.0
v0.19.0 - 25 Nov, 2020
A list of all issues and changes can be found in the v0.19.0 milestone.
Community
- Go Nightly users are encouraged to discuss issues and share feedback in the #vscode-go-nightly slack channel as well as the newly created Go Nightly mailing list (Issue 817)
- All experiments have been turned on for Go nightly (Issue 818)
Enhancements
- Added a snippet for TestMain (Issue 629)
- Added
lispcase
,pascalcase
andkeep
as transform variants for go.addTags (Issue 906, 936) - Added support for
gomodifytags
's --template flag (Issue 826) - Language Server
- Upgraded to the latest vscode-languageclient pre-release (Issue 42148)
- Debugging
- package.json: activate extension onDebugInitialConfigurations (Issue 131)
Fixes
- Fixed test streaming output handling to correctly add -json flag (Issue 471)
- Fixed bug that unnecessarily buffered test output (Issue 917)
- Fixed a bug that occurred when choosing a new Go environment using the file picker (Issue 868, 864)
- Hide running test StatusBarItem after cancelling tests
- Tool Installation
- Filter out unsupported document types to improve VS Code Live Share experience (Issue 605)
- Fixed language server survey computation error
- Debugging
- No longer shows a warning about editing Go files if there is no Go Debug Session running.
- Now removes user set '--gcflags' before passing the program to the debugger, since the debugger adds its own flags before building resulting in an error (Issue 117)
- Fixed bug where the working directory passed in by the user is ignored (Issue 918)
Code Health
- Debugging
- Improved the extension contributor experience by renaming the test fixtures folder to avoid errors being shown for these files
- Language Server Tests
- Adjusted home directory used in gerrit CI since recent changes in kokoro were restricting access (Issue 833)
- Updated Github workflows actions/setup-go to v2
- Restructured the goTest code to be more readable and easier to test
- Continued to improve the gopls settings documentation generator (Issue 197)
Thanks
Thank you for your contribution, @pofl, @hyangah, @perrito666, @pjweinbgo, @quoctruong, @stamblerre, @skaldesh, and @suzmue!