For instructions on installing the Dart or Flutter extensions, go here.
v2.7.3
- Typing a
{will no longer cause code completion to automatically appear unless it was immediately preceded by a$
v2.7.2
This version contains no functional changes but updates some internal references to the extension’s publisher ID which has been changed from DanTup to Dart-Code.
v2.7.1
- Further improvements have been made to reduce the chances of
printing JSON from Flutter apps from crashing the debugger - If during a hot reload, code that has changed was not re-executed (for example if you change the
mainmethod) you will now see a notification with an option to perform a hot restart - Long Dart SDK version numbers (git hashes) will now be truncated in the status bar (the full version is available in the tooltip)
v2.7.0
- When debugging, call stacks on Windows should no longer show long (incorrect) relative paths
- Find references will no longer hang with
Loading...if invoked somewhere that has no results (eg. keywords) - Code completion will no longer hang with
Loading...when using the Angular plugin and there are no results - Code completion will now trigger automatically after typing
$or{inside strings - Saving
pubspec.yamlin a Flutter project will no longer runpub getbut instead run the Flutter eqvuilent - Executing SDK commands will now pick a more appropriate workspace (or prompt for one if it cannot)
- Folders named
packagesthat contain real projects (like inside the Flutter repo) will now be detected more accurately (reducing package path resolution issues) - The Flutter debugger will no longer crash if you
printa JSON array - The Flutter debugger will no longer hang if you create breakpoinst prior to launching the debug session
- Vanilla Flutter projects inside the Fuchsia tree should now be treated like Flutter and not Fuchsia, enabling the Flutter deamon and debugging support
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!