Skip to content

gopls/v0.7.5

Compare
Choose a tag to compare
@findleyr findleyr released this 21 Jan 16:49
· 2477 commits to master since this release

Configuration changes

templateExtensions now defaults to []

Following feedback on the template features introduced with v0.7.4, we have made improvements to the way the active set of template files is configured. The templateExtensions setting is now empty by default, and gopls recognizes any open files with the "gotmpl" language identifier as a template file. As a result, unopened files will not be loaded as Go templates unless the templateExtensions is configured to be non-empty, but gopls will still provide template language features to any open files configured to be Go template files by the LSP client.

As always, your feedback helps make gopls better, and is greatly appreciated!

Features

New postfix completions

  • The split! completion on values of string type inserts a strings.Split snippet.
    split

  • The join! completion on values of []string type inserts a strings.Join snippet.
    join

New suggested fix for unused function parameters

The diagnostic for unused function parameters now includes a suggested fix to rename the parameter to _. This diagnostic is disabled by default, but can be enabled via the unusedparams setting in the analyses section.
unusedparam

UPDATE 2022-01-26: Final Support for Go 1.12

Due to compatibility issues, v0.7.5 will be the final gopls version to support building at Go 1.12. This is consistent with our stated goal of supporting the four most recent Go versions.

Longer term, we are planning features that will make it easier to build gopls with a recent Go version, but continue to develop projects for older Go versions. At that point we will begin to narrow our support window toward an eventual goal of supporting the two most recent Go versions. See golang/go#50825 for more details.

Fixes

A full list of all issues fixed can be found in the gopls/v0.7.5 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@pjweinb @suzmue @jba @A-UNDERSCORE-D