commit | a76ff6b2cf60f3c51e37bb9c008547f15bbe2466 | [log] [tgz] |
---|---|---|
author | Danny Tuppeny <danny@tuppeny.com> | Tue Aug 20 20:13:57 2024 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 20 20:13:57 2024 +0000 |
tree | b055f5a006d3888bb092eef0568c230104a2c74f | |
parent | 371948556dd6afa5a6a8d369b8e83553c61def88 [diff] |
[analysis_server] Add failing tests for analyzer plugin issue This adds failing tests for https://github.com/dart-lang/sdk/issues/56475. If this CL is applied to the 3.5 release and the `singleOptionContexts` flag set back to `true` (matching 3.4 behaviour), the tests will pass. Each package in both tests will get its own context root (because they have analysis_options to enable the plugins) and each one will read the correct plugins that are enabled. However if `singleOptionContexts` is `false` (as shipped in 3.5) or this code is applied to bleeding-edge (where the flag is gone, but behaves the same as `false`) both tests fail as follows: `test_sentToPlugins_inNestedPackages_withPackageConfigs` fails because we read the child analysis_options for the root and try to incorrectly load plugins from the root (and include duplicates and allow more than one plugin): ``` Expected: { 'package1': ['plugin1'], 'package2': ['plugin2'], 'package3': ['plugin1'] } Actual: { 'home': ['plugin1', 'plugin2', 'plugin1'], 'package1': ['plugin1', 'plugin2', 'plugin1'], 'package2': ['plugin1', 'plugin2', 'plugin1'], 'package3': ['plugin1'] } ``` `test_sentToPlugins_inNestedPackages_withoutPackageConfigs` fails because we now only have a context root for the root which enables all plugins from the children: ``` Expected: { 'package1': ['plugin1'], 'package2': ['plugin2'], 'package3': ['plugin1'] } Actual: { 'home': ['plugin1', 'plugin2', 'plugin1'] } ``` Change-Id: I12f45eeb5c1848352af26ac3fdb690e51833c22a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/381460 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Samuel Rawlins <srawlins@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.