VS Code extensions v3.110

372 views

Skip to first unread message

Danny Tuppeny

unread,

May 1, 2025, 9:24:26 AMMay 1

to flutter-...@googlegroups.com

Hi all,

New versions of the Dart/Flutter extensions for VS Code have been published! Release notes are below (and online).

Flutter

#5494: When enabling a new platform for a project, default files like test/test_main.dart are no longer recreated.
#5498: After selecting to enable a new platform, an additional confirmation prompt is no longer shown and the platform is enabled immediately.

Commands

#5500: The “Copy VM Service URI” command now provides options to copy both internal and exposed URIs when running in a remote session (such as SSH or Firebase Studio).
#5501: The “Copy VM Service URI” command no longer shows an error stating that there are no debug sessions available if you cancel from the debug session prompt.

Testing

#5489: In multi-root workspaces, workspace folder names are now included in the test runner tree labels.
#5488: Test suites are no longer sometimes duplicated in the test runner if they are both discovered statically and provide test results during a debug session.

Misc

#5490: analysis_options.yaml and .dart_tool have been added to the list of files that trigger activation of the Dart Extension. This may help the extension activate earlier when opening some workspaces where Dart projects are deeply nested if one of these files/folders still exist within the top few levels.
#5320: Starting with the upcoming v1.100 of VS Code (not the Dart extension), autocompletion in YAML files will automatically trigger when typing.

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 available to test in the current beta/master channels and will show up in future SDK releases.

#5496: “An error occurred while handling textDocument/rename request” no longer occurs when renaming a closure parameter.

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!