- #4306: Variable names that include reserved words within them are no longer colored incorrectly when using a theme that doesn’t support semantic tokens (or are disabled).
- #4300: Functions and methods named
set are no longer colored incorrectly when using a theme that doesn’t support semantic tokens (or are disabled).
implements clauses for classes with type parameters are no longer uncolored when using a theme that doesn’t support semantic tokens (or are disabled).
- #4294: Enabling a new target platform for a Flutter app through the device selector no longer silently fails to set up the platform.
- #4313: Enabling the new SDK DAPs for Flutter pre-release branches by default has been temporarily reverted pending a fix for https://github.com/dart-lang/sdk/issues/50802. The SDK DAPs can still be opted-in to using the
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 will show up automatically after you upgrade to the next (non-hotfix) Dart/Flutter SDK release. If you’re using a recent
master version, these items should be available to you and any issues should be reported on GitHub in the usual way.
- #4177: The Extract variable refactor now includes an explicit type when the
always_include_types lint is enabled.
- #4296: When using the new SDK DAPs, debugger views (Watch, Variables) no longer include private getters that always fail if the current stack frame is from in the library that declares them. These getters were already filtered out by the original/legacy DAPs.
- #4291: When using the new SDK DAPs in a remote workspace, URLs hosting Flutter web apps and the debug proxy backend are now correctly exposed/mapped so they are accessible to the local client.
- #4292: When using the new SDK DAPs in a remote workspace, Flutter web apps will now be automatically opened on the client (as was the case with original/legacy DAPs).
- #4293: When using the web-server device with the new SDK DAPs, it will be clearer when Flutter is waiting for you to click on the Dart Debug extension button in the launched browser window.
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!