Skip to content

Latest commit

 

History

History
569 lines (392 loc) · 39 KB

CHANGELOG.md

File metadata and controls

569 lines (392 loc) · 39 KB
Raw

v2.9.0

  • A new command (Flutter: New Project) has been created to simplify the process of creating and opening a new Flutter project (unlike others, this command is in the palette even without a project open)
  • Flutter and Dart debuggers have been merged, you will no longer be asked to choose between Flutter and Dart when running new projects!
    • As part of this, the type attribute on launch configurations in your launch.json will be automatically changed from dart-cli/flutter to dart upon opening the project
  • Flutter projects no longer require a launch.json file if being launched with default arguments; if you hit F5 in a project without one it will just launch immediately
  • If your packages are missing or out of date you will be prompted to run pub get/flutter packages get upon loading your project (this can be disabled with the new dart.promptToFetchPackages setting, which can be set at the folder level)
  • Snippets have been added for Flutter widgets (stless, stful, stanim) and will show only inside Flutter projects
  • Quick Fixes and other code actions that insert code now support tab stops and selections (for example the Wrap with new widget assist will now select the text widget for you to type over)
  • Code completions will no longer insert parentheses/argument placeholders if they are already present
  • Code completions will now longer insert named argument placeholders if a value is already present
  • A spinner will be shown in the status bar during analysis
  • A spinner will be shown in the status bar while Flutter/Pub commands are running
  • Quick fixes will now be sorted in the lighbulb menu by the severity of the error that they fix
  • Quick fixes and code assists are now categorised as QuickFix and Refactor in Code to allow for keybinding a specific type
  • SDKs will now be listed by version number in the SDK picker
  • Snippets will no longer be prioritised over other completions in the completions list
  • A workaround for a change in VS Code 1.20 that causes breakpoints to not be hit on Windows has been implemented
  • Package restore commands will now be terminated and re-run if you invoke them again while they are already running (this includes if you change pubspec.yaml and save)
  • Due to a number of issues with the implementation, external files (SDK, packages) will no longer open read-only (this behaviour may be restored in some form in future)
  • Executing package restore commands in a workspace that has no pubspec.yaml on Windows will no longer get the extension stuck in a loop
  • Saving pubspec.yaml in a Dart project will no longer run flutter packages get if you have a Flutter project in the same workspace
  • Fetching flutter packages will no longer sometimes unexpectedly ask you for the workspace folder to run the command in
  • Opening a Dart file outside of a folder will no longer show errors in the developer console
  • A new setting (dart.previewDart2) has been added which allows you to opt-in to Dart 2 behaviour such as optional new/const (you must be using an SDK that supports this!)

v2.8.2

  • Code completion has been updated to use a new field provided by the analysis server that allows the text to be inserted to be different from the text displayed in the completion

v2.8.1

Code 1.20.0 included a change that broke debugging for projects without a launch.json. A fix is on its way but in the meantime a workaround has been added to restore the ability to debug. As a consequence you will need to select the correct debug type twice when first debugging a project with no launch.json but this will be addressed in a future update (after Code's fixes are live).

v2.8.0

  • Code completion will automatically trigger when manually typing import " to help complete package/filenames
  • Code completion will automatically trigger in the correct location when completing the import ""; snippet to help complete package/filenames
  • The document symbol list will no longer fail to load for documents returning CONSTRUCTOR_INVOCATION symbols in results
  • Code completion will no longer fail to load for documents returning CONSTRUCTOR_INVOCATION symbols in results
  • The debug adapter should no longer crash if you print() JSON that looks like a flutter command while debugging a flutter application (additional improvements over those already made in previous releases)
  • Debug status text like "Initializing hot reload" will no longer remain visible if you terminate a debugging session while it is visible
  • The "Full restart recommended" hint has been moved from an information bar at the top of the window to the status bar
  • Pressing the debuggers Restart button to perform a hot reload will no longer crash if you have unsaved changes
  • Invoking Save All will no longer cause multiple hot reload requests which could result in crashes
  • If a hot reload is requested while another is in progress, the message "Reload already in progress" will be displayed in the debug output and the request ignored

v2.7.3

  • Typing a { will no longer cause code completion to automatically appear unless it was immediately preceeded 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 main method) you will now see a notification with an option to perform a full 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 pubspac.yaml in a Flutter project will no longer run pub get but instead run the Flutter eqvuilent
  • Executing SDK commands will now pick a more appropriate workspace (or prompt for one if it cannot)
  • Folders named packages that 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 print a 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

v2.6.2

  • An issue with pub and flutter commands not working from the command palette (introduced in v2.6.0) has been fixed

Preview Features available in this version

v2.6.1

  • The error message displayed when the analysis server cannot be found is more useful (previously it incorrectly reported that it had terminated)
  • An issue where the analysis server was not found if the dart executable in your PATH is a symlink (introduced in v2.6.0) has been fixed

Preview Features available in this version

v2.6.0

Note: This version requires Visual Studio Code 1.18.

Multi-root support

VS Code 1.18 gained support for multi-root workspaces, which allows multiple folders to opened at the same time. Perviously, much of Dart Code's functionality would just act on the first folder in the list. Now, all functionality should work as you would expect.

  • When adding a Flutter or Fuchsia project to a multi-root workspace that didn't previously have one, you will be prompted to reload to allow switching to the correct SDK
  • When running Flutter/Pub commands with multiple projects open, you will be prompted to select which folder to execute them for
  • Several settings have been promoted to resource-level which allows them to be set at a folder level even inside a multi-root workspace:
    • dart.insertArgumentPlaceholders
    • dart.lineLength
    • dart.pubAdditionalArgs
    • dart.runPubGetOnPubspecChanges
    • dart.flutterRunLogFile
    • dart.debugSdkLibraries
    • dart.debugExternalLibraries
    • dart.observatoryLogFile
  • Settings not listed above as resource-level must now be set at a User or Workspace level (VS Code will highlight such settings if you set them at a folder level)
  • The Dependency tree is hidden when you are working in a multi-rook workspace

Other Changes

  • SDK search paths have been simplified to make them easy to understand when trying to diagnose missing SDK issues
  • The dart.sdkContainer setting has been renamed to dart.sdkPaths and an array of multiple paths (this allows you to list several SDKs or folders full of SDKs can quickly switch between them using the SDK Version in the status bar)
  • The SDK Version switcher is now available for Flutter and Fuchsia projects
  • A new setting has been added to override the Flutter SDK location (dart.flutterSdkPath)
  • SDK overrides now apply to all project type (Fuchsia, Flutter, Dart)
  • The depdency tree will no longer appear in the explorer pane when there are no dependencies to show

Preview Features available in this version

v2.5.1

  • Chinese characters in paths should no longer result in breakpoints not being hit during debugging

Preview Features available in this version

v2.5.0

  • A new Open Observatory command is now available during Dart and Flutter debugging sessions to launch Observatory in a browser
  • A new Open Timeline command is now available during Flutter debugging sessions to launch the Observatory Timeline in a browser
  • Closing Labels are now enabled by default when you are using a version of the SDK that supports it
    • A new option (dart.closingLabels) has been added to allow these to be disabled
  • The setting dart.flutterHotReloadOnSave now defaults to true and will force a hot reload upon saving (if there are no errors in the file being saved)
  • Progress messages will now be shown in the status bar when building/debugging Flutter projects
  • Characters typed at the end of a line will no longer appear after the Closing Labels
  • The dart.sdkContainer option (which adds a quick "SDK Picker") now works if pointing directly at an SDK instead of its parent

Preview Features available in this version

v2.4.4

  • The search path for the Flutter SDK cached by Fuchsia has been updated in line with the latest Fuchsia code
  • The dart.userDefinedSdkPath setting will now override the Dart SDK used for Fuchsia projects (this is temporary until Fuchsia and Flutter get their own override)

Preview Features available in this version

v2.4.3

Note: This version requires Visual Studio Code 1.17.

  • The search path for the Dart SDK in Fuchsia projects has been updated to reflect the new location in a third_party folder
  • Several debug APIs are being removed in Code 1.18 so Dart Code has been moved off them - these should have no visible effects but since there was a lot of refactoring there is risk of new bugs in:
    • Code that provides debug configurations for new projects that do not have a .vscode/launch.json file
    • Code that supplements the launch config with things like SDK paths before passing to the debug adapter
    • Code that passes custom commands (like Flutter's hot reload, toggle debug painting, etc.) from the IDE to the debug adapter

Preview Features available in this version

v2.4.2

  • The Closing Labels preview feature will no longer show a toast popup asking for feedback every time it activates

Preview Features available in this version

v2.4.1

Note: This version requires Visual Studio Code 1.16.

  • Tooltips for items with no dartdocs will now appear correctly (a breaking change in Code 1.16 resulted in these disappearing)
  • The text colour for Closing Labels preview can now be controlled using the dart.closingLabels colour (you can set this in your settings, inside the workbench.colorCustomizations section - see here)
  • Go-to-Definition will no longer sometimes open some files inside your own project as read-only on Windows because of path casing differences
  • TODOs will now appear with lower priority than lints and hints in the Problems pane
  • The error message shown when the Flutter SDK cannot be find will now correctly refer to the FLUTTER_ROOT environment variable instead of FLUTTER_HOME

Preview Features available in this version

v2.4.0

  • Dart Code will now activate if a workspace contains a .dart file rather than only if it contains a pubspec.yaml file or when a .dart file is specifically opened
  • The dependency tree should work more reliably for .packages files that are not consistent with those generated by pub (for example, the hand-maintaned one in the Dart SDK repo)
  • Errors that occur when running Flutter debug commands will now be shown in the debug console
  • The Closing Labels preview has been updated to use functionality provided by the Dart SDK which will result in better performance and improved labels (this requires SDK v1.25.0-dev.11.0 or later)

Preview Features available in this version

v2.3.5

  • When working with a project that does not have trailing slashes on paths in the .packages file (such as dart-lang/sdk) breakpoints in packages should now work as expected.

Preview Features available in this version

v2.3.4

  • Go-to-Definition now works in read-only files (eg. SDK or external files opened using Go-to-Definition)

Preview Features available in this version

v2.3.3

  • The dependency tree will now update after packages are changed/updated
  • When opening a Fuchsia project, the explorer will no longer indefinitely show a progress bar caused by trying to read dependencies
  • When using Go to Definition, files that are outside of your workspace root (eg. packages, SDK sources) will now be readonly to avoid accidental modification

Preview Features available in this version

v2.3.2

  • A new "Packages Tree" has been added to the explorer which lists your projects depencies and allows you to browse them in a read-only view
  • The ability to switch SDKs has been removed for Flutter and Fuchsia projects where it does not make sense
  • Fuchsia projects are now detected and will use the correct Dart SDK from Fuchsia
  • The dart.previewFlutterCloseTagDecorations preview feature has had several improvements
    • Decorations now appear in Fuchsia projects as well as Flutter projects
    • Decorations now appear for any Widget-returning method instead of only methods named build
    • Decorations will update less frequently to avoid flickering during quick typing
    • Decorations should no longer appear in invalid places (probably)
    • Decorations now look more like comments, prefixed with // instead of /
    • Decorations now apply to const constructor calls as well as those using new

Preview Features available in this version

v2.3.1

  • An issue with searching symbols in a file being unreliable (appearing to hang) has been fixed
  • A new setting flutterHotReloadOnSave has been added to force a hot reload upon saving (if there are no errors in the file being saved)
  • A new Full Restart command is now available during Flutter debugging sessions for a full restart

Preview Features available in this version

v2.3.0 - Flutter Debugging Commands

Several new commands have been added to aid Flutter debugging. These appear in the command palette but can be bound to keys in the Keyboard Shortcuts window in Code.

  • Toggle Debug Painting
  • Toggle Performance Overlay
  • Toggle Slow Animations
  • Toggle Repaint Rainbow
  • Toggle Platform (Android/iOS)
  • Toggle Baseline Painting
  • Toggle Slow-Mode Banner

Additionally the default hotkey for Organize Directives has been removed to avoid a warning from Code about modifier keys. You can rebind this command in Code's Keyboard Shortcuts window.

v2.2.0

  • When running on Mac OS + iOS breakpoints should work from first launch without having to hot reload first
  • A new Sort Members command has been added
  • Start without debugging will no longer error if this is the first time running a project (where the .vscode\launch.json file does not exist)
  • A new setting sdkContainer has been added which can be used for fast SDK switching - set to a folder that contains multiple SDKs and the Dart SDK version in the status bar will become clickable

v2.1.0

  • [Flutter] A new command has been added to the command palette to run flutter doctor
  • Dart and Flutter SDKs are now found in PATH even when they start with ~/ for a users home directory
  • All path names in config (log files, analyzer path, SDK path) now support starting with ~/ for a users home directory
  • When enabled, debug logging should now flush correctly before terminating to reduce the changes of data not being recorded
  • A new setting has been introduced (showLintNames) which will prefix lint/hint names into messages in the Problems pane to make it easier to // ignore them if you wish

v2.0.0 - Flutter Run/Debug/Reload Support!

Note: If you previously installed a beta version of Dart Code to help with testing Flutter integration, please uninstall it and close all Code instances before installing v2.0 from the marketplace.

  • [Flutter] When opening a Flutter project your selected device will be shown in the status bar
  • [Flutter] If you have more than one connected device you will be able to switch between them by clicking on the device in the status bar
  • [Flutter] Pressing F5 will build and launch your app on the selected device
  • [Flutter] The usual debugging experience is available for Flutter apps, including breakpoints, call stacks, watch window etc.
  • [Flutter] The debugger's Restart button (or Ctrl+Shift+F5) has been mapped to Flutter's hot reload and will update the running application without needing to rebuild
  • [Flutter] Code completion for Widgets will no longer show trailing commas in the list (though they will still be inserted)
  • Clicking the debugger's restart button for a Dart CLI app will no longer crash but instead provide a more useful message about being unable to restart when VS Code does not supply toe correct configuration (this issue is fixed for VS Code 1.14 coming soon)
  • Stack frame text when stopped in the debugger is now improved and will show async gaps
  • Cursor placement after code fixes and assists should now be more accurate

The contributing file has also been updated to make it easier to get started with contributing to Dart Code.

v1.4.2

Note: This version requires Visual Studio Code 1.13.

  • Code completion will now show types for named arguments more reliably
  • Argument placeholders will now (again) insert placeholder text instead of empty strings
  • Completing methods that take no arguments will no longer place the cursor between the parens as if there are arguments to type
  • When selecting items from the code completion list the cursor will now more reliably move to the expected location after insertion
  • New snippets have been added for test and group methods defined in the test package
  • Dart Code will now activate when opening workspaces that include a pubspec.yaml anywhere in the tree, not just in the workspace root folder
  • Debug logging will no longer appear in the Debug Output window when launching a debug session
  • Snippets now have slightly more verbose descriptions of their functionality

v1.4.1

  • Identifiers that start or end with $ symbols will now highlight correctly
  • Highlighting of variables inside interpolated strings is now more accurate
  • Configuration snippets have been added to make adding additional debug configs to launch.json easier

v1.4.0

  • Code assists are now available and will show up as lightbulbs similar to existing code fixes (for example, Wrap in new widget in Flutter projects)
  • Code completion will now refresh on certain key presses (space, (, =) which should result in more accurate results more often
  • Code completion results are now sorted by relevance rather than alphabetically
  • Cursor position should now be better maintained when executing code fixes
  • pubspec.yaml and analysisoptions.yaml will once again use the built-in YAML language/highlighting
  • When opening a flutter project, the .packages file will now also be used when trying to locate the Flutter SDK
  • The error message shown when unable to locate the Flutter SDK has been simplified and a link to the Flutter download page added
  • The environment variable FLUTTER_HOME is not recommended for use and will no longer be used to locate a Flutter SDK (FLUTTER_ROOT is still checked)

v1.3.0

  • When opening a Flutter project, the below locations will be checked for a Flutter SDK and the embedded Dart SDK will be used (if no flutter SDK is found an error message will be shown)
    • .\bin\flutter(.bat)
    • (FLUTTER_ROOT)\bin\flutter(.bat)
    • All folders in PATH
  • Dart SDK update checks are now disabled for Flutter projects due to the embedded Dartk SDK
  • Pub commands are now generally replaced with Flutter equivilents when a Flutter project is open (note: Pub commands still appear in the command palette for familiarity but will execute flutters versions)
  • When flutter: sdk: flutter is added to/removed from pubspec.yaml you will be prompted to reload to switch between Dart/Flutter SDKs
  • Pub commands will no longer appear in the command palette when a Dart project is not open

v1.2.0

  • The change made in v1.1.0 to support opening the Flutter repo introduced some new issues and has been reverted except for specific workspaces. The issue is caused by using a folder named packages which is not currently supported by the analyzer. In order to fix the issue for the Flutter repo the workaround will be triggered by the presence of a .\packages\.gitignore file (which exists in the Flutter repo but not in packages folders created by pub). This workaround will be removed once the Analyzer has been updated.

v1.1.0

  • Opening a folder that is not itself a Dart package but contains others (such as the Flutter repository) will no longer give false errors/warnings caused by incorrect package resolution
  • Setting Dart SDK/libraries as debuggable/non-debuggable will now work correctly with SDK 1.23 which has different debugging defaults
  • The launch.json file should now be much simpler than before and not contain internal Dart Code settings that are not relevant to the user *
  • The launch.json file now properly supports default so checkedMode: true and args: [] are not longer required unless being changed *

* Your launch.json file should automatically be tidied up when you first open your project.

v1.0.2

  • interface has been removed from the list of keywords for syntax highlighting. It has not been a Dart keyword for sometime and resulted in incorrect colouring when using it as a variable name
  • Expressions in interpolated strings should now be highlighted even when containing properties and method calls

v1.0.1

  • Opening a Dart file from the Dart SDK (such as navigating via Go to Definition on an SDK type) when using a dev-version 1.23 Dart SDK will no longer result in an infinite analyzing loop causing Analyzing... to flicker on the status bar

v1.0.0

  • Pressing F5 to launch Dart programs after upgrading to Code 1.10 will no longer fail with an error about an unexpected token in launch.json
  • Pressing F5 to launch Dart programs will now use Dart's checked mode by default
  • A new setting has been introduced (pubAdditionalArgs) that allows additional arguments to be passed to pub in the Pub Get and Pub Upgrade commands (this may be useful if you wish to use --packages-dir)
  • The order of items in error reports have been tweaked slightly to move more useful stuff further up

v0.15.1

  • Fixed an issue introduced in v0.15.0 where null would something appear in tooltips for items with no doc comments.

v0.15.0

  • Tooltips will now show include the name of the library that a type comes from.
  • When the Organize Directives command fails (eg. due to a compile error) the correct message will be displayed instead of [Object object]

v0.14.9

  • Completing named arguments that already have values will no longer cause the argument name to be inserted twice.

v0.14.8

  • An error message about the "new driver" will no longer appear when using version v1.22.0-dev.5.0 or later of the Dart SDK.

v0.14.7

Note: This version requires Visual Studio Code 1.8.

  • Code completion will no longer insert underscore characters after upgrading to Code 1.8.

v0.14.6

  • Using the experimental analysis driver will no longer result multiple error reports being offered when an error occurs

v0.14.5

  • Passing additional arguments to the analysis server via the hidden setting dart.analyzerAdditionalArgs now works as expected
  • Generated error reports will now include which analysis server arguments were used
  • Generated error reports will now include which type of request the server was processing
  • Generated error reports may now include additional diagnostic information from the analysis server
  • Generated error reports will now include some intro text encouraging the user to review the report for any sensitive information

v0.14.4

  • Some additional debugging settings have been added to help track down analysis server issues
  • Changing analysis server debug settings will now prompt you to reload the project to restart the analysis server
  • Some minor tweaks have been made to the error report generation when the analysis service crashes
  • Exception analytics should no longer sometimes include users source code paths/filenames in logs

v0.14.3

  • When changing the dart.sdkPath setting you will now be prompted (and given a button) to reload the project
  • If the analysis service crashes and analytics are enabled, the first line of the error message will be included in an analytics event

v0.14.2

  • Fix to fix for analytics :(
  • Add timings for extension activation and analysis server startup

v0.14.1

  • Minor update to improve session handling for analytics

v0.14.0

Note: Due to use of new APIs, Dart Code v0.14 requires Visual Studio Code v1.6 or newer.

Debug Just My Code

New settings have been added controlling whether to step into SDK and external library code when debugging. When first opening Dart Code with this change you will be prompted to choose whether to "Debug just my code" or "Debug all code". You can change this at any time with the dart.debugSdkLibraries and dart.debugExternalLibraries settings.

Analysis Server Error Reporting

If the analysis server encounters an error you will now be prompted (up to 3 times per session) to report the issue to the Dart team. Clicking "Generate error report" will build a document of markdown that you can simple copy/paste directly into the Dart SDK issue tracker (linked at the top of the report).

Misc

v0.13.1

  • Code completion should no longer occasionally fail showing Loading...
  • Invoking Go to Definition on import statements should no longer occasionally fail silently

v0.13.0

  • Support has been added to format documents while typing (you must enable editor.formatOnType). This currently triggers when you type ; or }. Please send feedback!

v0.12.0

  • A new "type hierarchy" feature has been added (F4)
  • The "Preview" tag has been removed from Dart Code
  • The VS Code version number is now included in analytics to help make decisions about when code supporting older versions of Code can be removed

v0.11.2

  • If the Dart analysis server crashes you will now be prompted to save and reload the project (rather than everything being silently broken)

v0.11.1

  • A new setting has been added (dart.insertArgumentPlaceholders) to turn off placeholder insertion during completion operations
  • More improvements have been made to hovers (these appear best in Code 1.6, currently the Insiders build)
  • Large lists will now be "paged" in the debugger locals/watch windows to improve performance
  • The SDK update notification now has a button to jump directly to the Dart SDK download page

v0.11.0

  • Code fixes have been added! Use Ctrl+. for the lightbulb menu or F8 for diagnostics widget
  • pub get will run automatically when you save pubspec.yaml (can be disabled with the dart.runPubGetOnPubspecChanges setting)
  • Completion for methods/constructors now adds placeholders for mandatory arguments
  • Completion for named arguments now adds a placeholder for the value
  • Pressing <ENTER> in a triple-slash comment (/// ...) will now pre-complete the comment markers for the next line
  • Pressing <ENTER> in an old-style multiline comment (/** ... */) will now pre-complete following lines and place the closing marker (*/) in the right position
  • Hovers will no longer contain hyperlinks that don't work when docs reference other elements
  • Display improvements to hovers/tooltips (these are not finished and will continue to be improvedin future releases)
  • Completion now shows when an element is deprecated
  • Hovers will now show when an element is deprecated (note: requires Dart SDK 1.20, currently unreleased)

Additionally there were some performance improvements, the beginning of automated testing and some additional diagnostic settings (to help users provide more detailed information if they encounter bugs).

Many bugs have been fixed by Microsoft and the Dart team that affect Dart Code so please be sure to upgrade to the latest versions of Code (1.5) and the Dart SDK (1.19.1).

v0.10.0

  • Debug support has been added! Breakpoints, hover evaluation, watch window, call stack etc. should all work (with some minor known issues)
  • Rename (F2) now works for most items
  • The update check for SDKs now connects to the internet to check for updates instead of using a hard-coded last-known-update value
  • A new setting has been added to disable SDK update checks/notifications (dart.checkForSdkUpdates)
  • Properties will now display better in completion/symbol lists and not as callable methods
  • SDK paths that have been removed from settings will no longer continue to be searched at startup
  • Indent settings for pubspec.yaml and analysis_options.yaml will now also be forced into 2-spaces at load (if dart.setIndentation has not been set to false)

v0.9.0

  • A warning will be shown at startup if your Dart SDK is older than the one the current Dart Code was tested with
  • If you have multiple open Dart projects using different versions of the SDK, running a command line app (F5) will no longer use the SDK from the last Dart project opened
  • Various improvements have been made to the display of search results and code-completion items
  • Snippets have been added for common code (main, try, switch, import, class, typedef and more!)
  • Errors will no longer occur trying to run pub get or pub upgrade if your SDK is in a path that contains spaces

v0.8.2

  • The display of symbols in the workspace symbol search (Ctrl+T) has been improved *
  • The Dart language service will no longer crash when you enter symbols into the (Ctrl+T) search box
  • Pressing F5 will now allow you to run a Dart command line application (you will need to set the path in .vscode\launch.json) **
  • Organize Directives (ctrl+alt+o) has been added

v0.7.0

  • Workspace symbol search (Ctrl+T) now includes more symbols from your workspace including imported packages
  • Document symbol list/search has been implemented (Ctrl+Shift+O)
  • Document highlights have been implemented (selected a symbol will highlight other instances)
  • Commands for pub get and pub ugprade have been added
  • Errors and warnings from files that are deleted when not open will no longer hang around in the problems view

v0.6.2

  • Find References (Shift+F12) has been added
  • Open files are given higher priority for analysis operations
  • The extension no longer tries (and fails) to analyze open files that are outside of workspace folder

Additionally, a new option dart.allowAnalytics was added to control if analytics are sent. Only very basic events are captured (such as extension activation and if you toggle certain features) and are sent along with the extention version/platform. No code, filenames, project names or personal information will be sent. Source code for all analytics is visible here.

v0.6.1

  • A new setting dart.showTodos (default: true) has been added to show/hide TODO messages from the Problems list
  • "Analyzing…" will now show in the status bar when files are being analyzed
  • Go to Definition is now supported within your project (though does not yet work with SDK classes)
  • The Dart SDK version number will now show in the bottom right status bar
  • Dart files will automatically be set to 2-space indenting when you open them
  • A new setting dart.setIndentation (default: true) has been added to enable/disable automatic indent settings
  • Symbol search is now case-insensitive and also supports better filtering (eg. "TA" will match "TwitterApi")
  • Tooltips reading undefined will no longer appear for some items (eg. string literals)
  • Tooltip formatting/display has been greatly improved

v0.5.2

  • SDK detection is more reliable on Linux/Mac
  • Name changed from "Dart-Code" to "Dart Code"
  • Setting added to control line-width passed to formatter
  • Last used SDK path is cached to improve startup performance
  • Tooltip hovers now indicate the range that they apply to
  • Braces/quotes now automatically close
  • Pressing enter between a set of braces will automatically indent

v0.1.0

  • Syntax highlighting
  • Code-completion
  • Diagnostics (errors/warnings/hints)
  • Workspace-wide symbol search
  • Reformatting document
  • Tooltips