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
d67af7f CHANGELOG.md: v0.35.0 changelog
6ce6b54 src/goToolsInformation: update hardcoded latest version of gopls for release
19f6e6b package.json: add markdown descriptions to inlay hints config
d2f0f1c src/goTools: allow to install dlv for arm64
180bbce Substitute workspaceFolderBasename variable into extension settings
e63f1ad add support for multi-file test suite
05edb9c package.json: clean up formatter setting
b9472fc package.json: update gts (4.0.0), moment (2.29.4)
2de6d67 package.json: sync doc with [email protected]fdf5608 CHANGELOG.md: v0.34.1 changelog
99369b6 src/language/goLanguageServer: remove redundant error popups from custom error handler
4dd972e src/language/goLanguageServer: do not require gopls when language server is disabled
ee683d7 vscode-go: add inlay hint settings to extension config
0848778 src/goVulncheck: add actions to upgrade modules
78149ef src/goVulncheck: report unaffecting vulnerabilities separately
445a42f tools/goplssetting: omit inlay hints from gopls settings
8dfd393 src/commands: catch errors when starting language server
16009b2 package.json: update dev version
7efa03c .vscode: remove accidentally added MOCHA_GREP
Change-Id: Ibe77ea8285506f5d04d0ba6f6b6bb3252a3b61a9
Copy file name to clipboardExpand all lines: CHANGELOG.md
+16Lines changed: 16 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,19 @@
1
+
## v0.35.0 - 13 July, 2022
2
+
3
+
A list of all issues and changes can be found in the [v0.35.0 milestone](https://github.com/golang/vscode-go/milestone/47) and [commit history](https://github.com/golang/vscode-go/compare/v0.34.1...v0.35.0).
4
+
5
+
### Features
6
+
- This release adds support for inlay hints ([Issue 1631](https://github.com/golang/vscode-go/issues/1631)).
7
+
- Add logic to support ${workspaceFolderBasename} substitution in extension settings ([Issue 2310](https://github.com/golang/vscode-go/issues/2310)).
8
+
- Add support for multi-file test suite ([Issue 1130](https://github.com/golang/vscode-go/issues/1130)).
9
+
- Add support for custom formatters.
10
+
11
+
### Bug Fix
12
+
- Fixed (Issue [2339](https://github.com/golang/vscode-go/issues/#2339)) that prevented updating delve on arm64 Macs.
13
+
14
+
### Thanks
15
+
Thank you for your contribution, @hyangah, @nirhaas, @bentekkie, @jamalc, and @suzmue.
16
+
1
17
## v0.34.1 - 30 June, 2022
2
18
3
19
A list of all issues and changes can be found in the [v0.34.1 milestone](https://github.com/golang/vscode-go/milestone/48) and [commit history](https://github.com/golang/vscode-go/compare/v0.34.0...v0.34.1).
Copy file name to clipboardExpand all lines: docs/settings.md
+87-11Lines changed: 87 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -223,16 +223,8 @@ Default:
223
223
Flags to pass to format tool (e.g. ["-s"]). Not applicable when using the language server.
224
224
### `go.formatTool`
225
225
226
-
Not applicable when using the language server. Choosing 'goimports', 'goreturns', or 'gofumports' will add missing imports and remove unused imports.<br/>
227
-
Allowed Options:
228
-
229
-
*`default`: If the language server is enabled, format via the language server, which already supports gofmt, goimports, goreturns, and gofumpt. Otherwise, goimports.
230
-
*`gofmt`: Formats the file according to the standard Go style.
231
-
*`goimports`: Organizes imports and formats the file with gofmt.
232
-
*`goformat`: Configurable gofmt, see https://github.com/mbenkmann/goformat.
233
-
*`gofumpt`: Stricter version of gofmt, see https://github.com/mvdan/gofumpt.
234
-
*`gofumports`: Applies gofumpt formatting and organizes imports.
235
-
226
+
When the language server is enabled and one of default/gofmt/goimports/gofumpt is chosen, the language server will handle formatting. Otherwise, the extension will use the specified tool for formatting.<br/>
Enable/disable inlay hints for variable types in range statements.
351
+
```go
352
+
353
+
for k /*int*/, v /*string*/ := range []string{} { ... }
354
+
```
355
+
280
356
Default: `false`
281
357
### `go.installDependenciesWhenBuilding`
282
358
@@ -736,7 +812,7 @@ Example Usage:
736
812
|`deepequalerrors`| check for calls of reflect.DeepEqual on error values <br/> The deepequalerrors checker looks for calls of the form: <br/> reflect.DeepEqual(err1, err2) <br/> where err1 and err2 are errors. Using reflect.DeepEqual to compare errors is discouraged. <br/> Default: `true`|
737
813
|`embed`| check for //go:embed directive import <br/> This analyzer checks that the embed package is imported when source code contains //go:embed comment directives. The embed package must be imported for //go:embed directives to function.import _ "embed". <br/> Default: `true`|
738
814
|`errorsas`| report passing non-pointer or non-error values to errors.As <br/> The errorsas analysis reports calls to errors.As where the type of the second argument is not a pointer to a type implementing error. <br/> Default: `true`|
739
-
|`fieldalignment`| find structs that would use less memory if their fields were sorted <br/> This analyzer find structs that can be rearranged to use less memory, and provides a suggested edit with the optimal order. <br/> Note that there are two different diagnostics reported. One checks struct size, and the other reports "pointer bytes" used. Pointer bytes is how many bytes of the object that the garbage collector has to potentially scan for pointers, for example: <br/> <pre>struct { uint32; string }</pre><br/> have 16 pointer bytes because the garbage collector has to scan up through the string's inner pointer. <br/> <pre>struct { string; *uint32 }</pre><br/> has 24 pointer bytes because it has to scan further through the *uint32. <br/> <pre>struct { string; uint32 }</pre><br/> has 8 because it can stop immediately after the string pointer. <br/> <br/> Default: `false`|
815
+
| `fieldalignment` | find structs that would use less memory if their fields were sorted <br/> This analyzer find structs that can be rearranged to use less memory, and provides a suggested edit with the most compact order. <br/> Note that there are two different diagnostics reported. One checks struct size, and the other reports "pointer bytes" used. Pointer bytes is how many bytes of the object that the garbage collector has to potentially scan for pointers, for example: <br/> <pre>struct { uint32; string }</pre><br/> have 16 pointer bytes because the garbage collector has to scan up through the string's inner pointer. <br/> <pre>struct { string; *uint32 }</pre><br/> has 24 pointer bytes because it has to scan further through the *uint32. <br/> <pre>struct { string; uint32 }</pre><br/> has 8 because it can stop immediately after the string pointer. <br/> Be aware that the most compact order is not always the most efficient. In rare cases it may cause two variables each updated by its own goroutine to occupy the same CPU cache line, inducing a form of memory contention known as "false sharing" that slows down both goroutines. <br/> <br/> Default: `false` |
740
816
|`fillreturns`| suggest fixes for errors due to an incorrect number of return values <br/> This checker provides suggested fixes for type errors of the type "wrong number of return values (want %d, got %d)". For example: <pre>func m() (int, string, *bool, error) {<br/> return<br/>}</pre>will turn into <pre>func m() (int, string, *bool, error) {<br/> return 0, "", nil, nil<br/>}</pre><br/> This functionality is similar to https://github.com/sqs/goreturns. <br/> <br/> Default: `true`|
741
817
|`fillstruct`| note incomplete struct initializations <br/> This analyzer provides diagnostics for any struct literals that do not have any fields initialized. Because the suggested fix for this analysis is expensive to compute, callers should compute it separately, using the SuggestedFix function below. <br/> <br/> Default: `true`|
742
818
|`httpresponse`| check for mistakes using HTTP responses <br/> A common mistake when using the net/http package is to defer a function call to close the http.Response Body before checking the error that determines whether the response is valid: <br/> <pre>resp, err := http.Head(url)<br/>defer resp.Body.Close()<br/>if err != nil {<br/> log.Fatal(err)<br/>}<br/>// (defer statement belongs here)</pre><br/> This checker helps uncover latent nil dereference bugs by reporting a diagnostic for such mistakes. <br/> Default: `true`|
unaffectingContainer.innerHTML='<hr></hr><p>These vulnerabilities exist in required modules, but no vulnerable symbols are used.<br>No action is required. For more information, visit <a href="https://pkg.go.dev/vuln">https://pkg.go.dev/vuln</a></p>';
0 commit comments