-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
47 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| --- | ||
| title: v3.104 | ||
| sort_order: v0003_0104 | ||
| excerpt: "Dropping support for old SDKs, Flutter color previews, fixes..." | ||
| --- | ||
|
|
||
| # v3.104.0 _2025-02-03_ | ||
|
|
||
| ## Removing Support for Old SDK Versions | ||
|
|
||
| As [previously announced](https://groups.google.com/g/flutter-announce/c/JQHzM3FbBGI), support for older Dart/Flutter SDKs is being removed from the extension. This version of the extension (v3.104) is the last version that will work with SDKs earlier than Dart 3.0 and Flutter 3.10. If you're using an affected SDK, a one-time notification will be shown. | ||
|
|
||
| <img loading="lazy" src="/images/release_notes/v3.100/sdk_deprecation.png" width="560" height="220" /> | ||
|
|
||
| In the next release of the extension, code supporting these SDK versions will be removed. A table showing which extension versions support which SDKs (and instructions on how to change extension version) is available on the [SDK Compatibility page](/sdk-version-compatibility/) if you need to continue to use unsupported SDKs. | ||
|
|
||
| ## Color Previews in Code Completions | ||
|
|
||
| [#3941](https://github.com/Dart-Code/Dart-Code/issues/3941): When using the latest stable version of Flutter, in addition to the large dartdoc previews for the currently selected completion item, color previews are now shown inline against each color completion even when not selected. | ||
|
|
||
| <img loading="lazy" src="/images/release_notes/v3.102/completion_colors.png" width="800" height="400" /> | ||
|
|
||
| ## Improved Version Manager Support | ||
|
|
||
| [#5334](https://github.com/Dart-Code/Dart-Code/issues/5334)/[#5377](https://github.com/Dart-Code/Dart-Code/issues/5377)/[#5117](https://github.com/Dart-Code/Dart-Code/issues/5117): [@davidmartos96](https://github.com/davidmartos96) contributed new settings `dart.getFlutterSdkCommand` and `dart.getDartSdkCommand` that allow executing a command to locate the Dart/Flutter SDKs to use for a workspace. This improves compatibility with some SDK version managers (such as `mise` and `asdf`) because they can be queried for the current SDK instead of reading from `PATH` (or `package.json`). | ||
|
|
||
| ## Editor | ||
|
|
||
| - [#5378](https://github.com/Dart-Code/Dart-Code/issues/5378): The **Add 'x' to dependencies** quick-fix no longer tries to use a malformed package name when the imported URI contains more than one forward slash. | ||
|
|
||
| ## Misc | ||
|
|
||
| - [#5401](https://github.com/Dart-Code/Dart-Code/issues/5401): When using a VS Code workspace (`.code-workspace` file), relative paths in settings are now resolved relative to the folder containing the workspace file instead of the first folder in the workspace. | ||
|
|
||
| ## 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. | ||
|
|
||
| - [#5369](https://github.com/Dart-Code/Dart-Code/issues/5369): Functions assigned to local variables no longer fail to highlight other references correctly (instead, highlighting everything with the same name) when the text cursor is at their position. | ||
| - [#5365](https://github.com/Dart-Code/Dart-Code/issues/5365): Opening DevTools pages with the WASM experiment enabled no longer produces invalid URLs. | ||
| - [#5363](https://github.com/Dart-Code/Dart-Code/issues/5363): The debugger no longer incorrectly evaluates values for initializing parameters instead of class variables inside constructor bodies. | ||
| - [#5360](https://github.com/Dart-Code/Dart-Code/issues/5360)/[#4418](https://github.com/Dart-Code/Dart-Code/issues/4418): Stack traces printed to the Debug Console now have clickable links on the right hand side when the output has a prefix like `I/flutter`. | ||
| - [#5359](https://github.com/Dart-Code/Dart-Code/issues/5359): Diagnostics no longer produce "Illegal argument: character must be non-negative" errors that prevent diagnostics updating for some kinds of invalid parameters in constant constructor calls. | ||
| - [#5350](https://github.com/Dart-Code/Dart-Code/issues/5350): **Extract Method** now uses the newer `Function()` syntax avoiding some generating diagnostics for function types with unnamed parameters. | ||
| - [#5343](https://github.com/Dart-Code/Dart-Code/issues/5343): Lints no longer run for files that don't exist, which prevents a persistent `lower_case_with_underscores` diagnostic if a file tries to import a non-existant file with a violating name. | ||
|
|
||
|
|