VS Code extensions v3.82

349 views

Skip to first unread message

Danny Tuppeny

unread,

Feb 1, 2024, 11:02:34 AMFeb 1

to flutter-...@googlegroups.com

Hi all,

New versions of the VS Code extensions have been published. Release notes are below (and online).

Editor

#4552: The “Go to Super” command is now available on the editor context menu.
#4957: Methods named get/set that have type arguments are no longer coloured like keywords when Semantic Tokens are disabled (or unsupported by the theme).

DevTools

#4387: The dart.devtoolsLocation setting has been updated to allow specifying different settings for each DevTools page.

Before:

"devToolsLocation": "beside" // "beside" | "external" | "active"

After:

"dart.devToolsLocation": {
	"default": "beside", // A default used for any pages not explicitly configured
	"cpu-profiler": "external" // Open CPU profiler externally always
},

Debugger

#4966: The dart.previewSdkDaps setting has been replaced by a new dart.useLegacyDebugAdapters. The new setting has the opposite meaning (true means to use the legacy adapters, whereas for the old setting that was false).
#4930: Errors that occur when evaluating expressions (such as those triggered by Watch expressions that are no in scope) no longer trigger additional error notifications/toasts.
#4926: An issue that could cause Flutter apps to freeze when modifying breakpoints was fixed and hot-fixed into Flutter 3.16.9.

Misc

#4705/#4847: Notifications may now be shown suggesting other VS Code extensions appropriate for the project and packages you are using.

Features/Fixes Enabled with Future SDKs

The following items depend on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They may be able to test in the current beta/master channels and will show up in future SDK releases.

#4953: Using dart.customDevTools to run DevTools from source should no longer fail if there is no dart on PATH.
#4932: Global evaluation no longer fails with “Unable to find the library” when the open file is inside the lib folder of a package.
#4908: Fields on Record types are now colored the same way as fields on classes.
#4907: A “No thread with threadId x” error that could occur when terminating a debug session has been resolved.
#4899: The “Global evaluation not currently supported” message has been improved and no longer includes a verbose stack trace.
#4835: DevTools extensions can be opened from the sidebar.
#4952: DevTools extensions and other DevTools pages that are not specifically known to Dart-Code can now be opened embedded instead of only in an external browser.
#4821: DevTools can now be opened in an external browser (regardless of the dart.devToolsLocation setting) from the sidebar.
#4967: The “Deep Links” tool in a future version of DevTools will now be launchable from the command palette.

Upstream Issues

Some feature requests and fixes require new features and fixes in upstream projects like VS Code and LSP which use counts of 👍s on those issues to help gauge demand. The Dart-Code website now lists some of the most significant upstream issues with a description of the feature/fix they would enable. Please consider reviewing this list and adding your 👍 to any GitHub issues relevant to features you’d like to see!