| commit | 0677fcac838fcec7a3deff5d0aa6ae13bcd5a820 | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Thu Jun 19 02:49:24 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 19 02:49:24 2025 -0700 |
| tree | 2042b6a7a300784e5c685e24281895c2ce06d315 | |
| parent | 20dc41763a090ab976733e1fd37c15079988ebd0 [diff] |
[analyze] When opening several folders with "resolution: workspace" try to merge them by workspace root Use-case: I have 20+ folders from the sdk that I have open (front_end, _fe_analyzer_shared, vm, analyzer, analysis_server etc) and before this CL that meant I had 20+ contexts, despite them having `resolution: workspace` and being specified in the roots pubspec.yaml under `workspace`. Opening, for instance, `pkg` directly would successfully give me only 1 context, but also include lots of stuff I don't want to clutter neither my screen nor my mind. This CL merges such folders as possible meaning I with this CL only have 1 context. * If not using the workspace resolution this should change nothing. * If opening only the root of a workspace this should change nothing. * If opening a sub folder that itself isn't a package (say `pkg` in the sdk) this should change nothing. Change-Id: Ia38fa6636b02fa95ed274ebf72d424cae7d4da66 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/434802 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Jens Johansen <jensj@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.