For instructions on installing the Dart or Flutter extensions, go here.
- #3808: Attaching to a Flutter process started outside of VS Code no longer requires manual configuration of the
packagesfile in order for the debugger to correctly locate files while debugging/stepping. This fix applies only to the new SDK DAPs (which can be opted-in to using the
- #4152: The “Run”/”Debug” CodeLens links now appear on the line directly above the
mainmethod name, and not above the related DartDoc comments.
- #4178: In a multi-folder workspace, running a debug session without an explicit
cwdor one that can be inferred from
programwill now use the nearest common ancestor of all open workspace folders (if one can be found that is not the drive root).
- #4134: When using the Dart: Capture Logs commands, long lines are no longer truncated. Logs written to disk using the related settings are still truncated based on the
Rollout of New SDK Debug Adapters
#4194: Several issues that led to pausing the rollout of the new SDK debug adapters have been resolved in latest bleeding-edge builds of Dart/Flutter. As such, rollout will continue when using an SDK version with these fixes (which is currently only users of the Flutter/Dart master branches).
Additionally, users of pre-release SDKs (with a sufficient version number to include the fixes noted above) will immediately be opted-in to the new DAPs (skipping the progressive rollout used on the stable branch). If you notice any unexpected behaviour while debugging (or while not debugging 🙂) please file issues which as much detail as possible!
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 when you update your SDK in future (or sooner if using beta/development channels - depending on the exact version).
- #612: Call Hierarchy is now available (
H, or from the context menu).
- #4154/#3609/#4160: Inlay hints are now available for inferred types and parameter names (shown while holding
- #4143: Auto-imports now work when completing extension members.
- #4131: Renaming a symbol no longer updates DartDocs with unresolved identifiers of the same name.
- #4129: Go to Symbol in Workspace no longer navigates to the parent library file when using
- #4121: Code folding regions that overlap the same line (such as parameter list and function bodies) have been adjusted since VS Code recently stopped supporting them.
- #4120: Hovering over a constructor’s parameters no longer show an oversized font for the type.
- #4114: Navigation/resolution of DartDoc qualified references that reference members from a base class now work as expected.
- #3182: Code completion now offers members that can be overridden when invoked in a completely empty class.
- #4184: The Create missing override(s) quickfix now shows in completely empty classes.
- #4181: Links for the “See code in” example links in Flutter no longer return additional unexpected results when trying to navigate with Go to Definition /
- #4169: The Remove widget assist is now available on widget calls prefixed with aliases.
- #4167: The Inline Method refactor no longer fails if the method has type parameters.
- #4157: Find References once again works when the caret is at the end of the symbol name (or the entire symbol name is selected). This issue only affected some recent pre-release versions of the SDK.
- #4141: Hot Reload and Hot Restart now show progress notifications when using new SDK DAPs.
- #4101: The Debug Console now focuses more quickly when launching an app using the new Flutter SDK DAP.
- #3966: DevTools no longer sometimes fails to open if a previous window had been closed within the last 30 seconds.
- #4149: Breakpoints will no longer fail to be hit on Windows when using SDK DAPs depending on the casing of the drive letter of the current working directory.
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!