[analysis_server] Switch LSP tests to use workspaceAnalysisComplete() instead of progress/status notifications Progress/status notifications for analysis are not a reliably indicator of analysis being complete. They might not be sent if there is no work, or may have multiple bursts in case of plugins. The new `dart/workspace/analysis/complete` request was added as a reliably signal that all pending work is complete. This change updates all tests that used the progress/status notifications to know analysis had completed (except tests that were specifically testing the notifications), removing concepts like "initialAnalysis" which could be unsound with plugins (or debouncing of status notifications). I also replaced some `await pumpEventQueue();` which followed calls to the server with `await workspaceAnalysisComplete();` because it should also be more reliable. However `pumpEventQueue` remains when it's after synchronous modifications to the resource provider, since otherwise the server might not have started processing the watch event before we called it. Change-Id: I342890c82e18848b9bffc00876141216fbbcd5c7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/526482 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.