You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
how to configure gopls on vscode, I want to forbidden gopls analyzers
Most recent release: v0.4.1.
v0.4.1
This release contains mostly stability improvements and smaller bug fixes. A list of all of the issues fixed in this release can be found in the gopls/v0.4.1 milestone. A notable change is that type error analyzers (fillreturns, undeclaredname, unusedparams, nonewvars) are now on by default.
v0.4.0
Improved support for working with modules (@ridersofrohan). A detailed walk-through of the new features can be found here. A quick summary:
Use the -modfile flag to suggest which modules should be added/removed from the go.mod file, rather than editing it automatically.
Suggest dependency upgrades in-editor and provide additional language features, such as formatting, for the go.mod file.
Inverse implementations (@muirdm). "Go to implementations" on a concrete type will show the interfaces it implements.
Completion improvements (@muirdm). Specifically, improved completion for keywords. Also, offer if err != nil { return err } as a completion item.
Jumping to definition on an import statement returns all files as definition locations (@danishprakash).
Support for running go generate through the editor, via a code lens (@marwan-at-work).
Command-line support for workspace symbols (@daisuzu).
Opt-in:
Code actions suggesting gofmt -s-style simplifications (@ridersofrohan). To get these on-save, add the following setting:
Code actions suggesting fixes for type errors, such as missing return values (goreturns-style), undeclared names, unused parameters, and assignment statements that should be converted from := to = (@ridersofrohan). Add the following to your gopls settings to opt-in to these analyzers. In the future, they will be on by default and high-confidence suggested fixes may be applied on save. See additional documentation on analyzers here.
the Go project does not use its bug tracker for general discussion or asking questions about the language. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.
Please see the Questions wiki page; it has a list of good places for asking questions. Thanks!
how to configure gopls on vscode, I want to forbidden gopls analyzers
Most recent release: v0.4.1.
v0.4.1
This release contains mostly stability improvements and smaller bug fixes. A list of all of the issues fixed in this release can be found in the gopls/v0.4.1 milestone. A notable change is that type error analyzers (fillreturns, undeclaredname, unusedparams, nonewvars) are now on by default.
v0.4.0
-modfile
flag to suggest which modules should be added/removed from thego.mod
file, rather than editing it automatically.go.mod
file.if err != nil { return err }
as a completion item.go generate
through the editor, via a code lens (@marwan-at-work).Opt-in:
gofmt -s
-style simplifications (@ridersofrohan). To get these on-save, add the following setting::=
to=
(@ridersofrohan). Add the following to your gopls settings to opt-in to these analyzers. In the future, they will be on by default and high-confidence suggested fixes may be applied on save. See additional documentation on analyzers here.For a complete list of the issues resolved, see the gopls/v0.4.0 milestone.
Originally posted by @stamblerre in #33030 (comment)
The text was updated successfully, but these errors were encountered: