languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-10-01 17:12:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Changelog entry for .packages breaking change

Browse source 
Change-Id: I40d03b47a9f0e4ebe4d3c95d8ab8101a2fd0f7b7
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/251765
Reviewed-by: Kevin Moore <kevmoo@google.com>
Reviewed-by: Jonas Jensen <jonasfj@google.com>
This commit is contained in:
Michael Thomsen 2022-07-19 08:03:54 +00:00
parent f667180626
commit 04ae05beae
1 changed files with 32 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
CHANGELOG.md
View file

@ -52,12 +52,11 @@ them, you must set the lower bound on the SDK constraint for your package to
[language version]: https://dart.dev/guides/language/evolution
- **[Enhanced type inference for generic invocations with function
literals][]**: Invocations of generic methods/constructors that supply
function literal arguments now have improved type inference. This primarily
affects the `Iterable.fold` method. For example, in previous versions of
Dart, the compiler would fail to infer an appropriate type for the parameter
`a`:
- **[Enhanced type inference for generic invocations with function literals][]**:
Invocations of generic methods/constructors that supply function literal
arguments now have improved type inference. This primarily affects the
`Iterable.fold` method. For example, in previous versions of Dart, the
compiler would fail to infer an appropriate type for the parameter `a`:
```dart
void main() {
@ -90,6 +89,7 @@ them, you must set the lower bound on the SDK constraint for your package to
(a, b) => a == null || a < b ? b : a);
}
```
[Enhanced type inference for generic invocations with function literals]: https://github.com/dart-lang/language/issues/731
- **Breaking Change** [#48167](https://github.com/dart-lang/sdk/issues/48167):
Mixin of classes that don't extend `Object` is no longer supported:
@ -211,6 +211,30 @@ the new implementation carries a few subtle changes in behavior:
### Tools
#### General
- **Breaking Change** [#48272](https://github.com/dart-lang/sdk/issues/48272):
The `.packages` file has been fully discontinued. Historically when the
commands `dart pub get` or `flutter pub get` are executed, pub resolved all
dependencies, and installs those dependencies to the local pub cache. It
furthermore created a mapping from each used package to their location on the
local file system, and wrote that into two files:
* `.dart_tool/package_config.json`
* `.packages` (deprecated in Dart 2.8.0)
As of Dart 2.18.0, the `.packages` is now fully desupported, and all tools
distributed in, and based on, the Dart SDK no longer support it, and thus
solely use the `.dart_tool/package_config.json` file. If you've run `dart pub
get` or `flutter pub get` with any Dart SDK from the past few years you
already have a `.dart_tool/package_config.json` and thus should not be
impacted. You can delete any old `.packages` files.
If you have any third-party tools that for historical reasons depend on a
`.packages` we will support the ability to generate a `.packages` by passing
the flag `--legacy-packages-file` to `dart pub get`. This support will be
removed in a following stable release.
#### Dart command line
- **Breaking change** [#46100](https://github.com/dart-lang/sdk/issues/46100):
@ -255,9 +279,8 @@ Updated the Linter to `1.25.0`, which includes changes that
#### Pub
* Breaking: `dart pub get` and `dart pub upgrade` no longer creates the
[deprecated](https://github.com/dart-lang/sdk/issues/47431) `.packages` file.
It can still be created with the `--legacy-packages-file` flag.
* `dart pub get` and `dart pub upgrade` no longer create the
`.packages` file. For details, see breaking change #48272 above.
* `dart pub outdated` now shows which of your dependencies are discontinued.
* `dart pub publish` will now list all the files it is about to publish.