| commit | 378b71af77927fd71070b8bd3cb333a33820f3a7 | [log] [tgz] |
|---|---|---|
| author | Danny Tuppeny <danny@tuppeny.com> | Tue Aug 27 10:14:26 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 27 10:14:26 2024 +0000 |
| tree | 590f4791f0ccf97f7396eac24351802199638273 | |
| parent | b9d83afb8a23c7b88fd019c38d531424744be366 [diff] |
[stable] Fix analysis server plugins not receiving setContextRoots (or having wrong roots) This is a cherry-pick of a76ff6b2cf60f3c51e37bb9c008547f15bbe2466 and c0c697bebefe30ea673ffe0a1f54621b3990eb70 which resolves an issue where analysis server plugins may not receive `setContextRoots` requests or may receive the wrong context roots due to the changes to not create an analysis context for every folder containing an `analysis_options.yaml` file. This change forces an analysis context for each folder that changes the set of plugins that are enabled compared to its parent, so that each "plugin root" is once again an analysis context root. Bug: https://github.com/dart-lang/sdk/issues/56475 Change-Id: Ia561d7ecf7429711a1059b0d77fc1929629b75cc Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/381460 Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/381481 Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/381860 Cherry-pick-request: https://github.com/dart-lang/sdk/issues/56547 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/381760 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Samuel Rawlins <srawlins@google.com> Reviewed-by: Phil Quitslund <pquitslund@google.com> Commit-Queue: Alexander Thomas <athom@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.