| commit | 895093e9f91972c984321149294c00e7f4f89f07 | [log] [tgz] |
|---|---|---|
| author | Sam Rawlins <srawlins@google.com> | Thu Aug 29 16:03:42 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 29 16:03:42 2024 +0000 |
| tree | f04eeae0fd76349d0db626734011fe6926d4e340 | |
| parent | 162a35f6542a48d6b2084c459a10e7c755cd007f [diff] |
Initial PluginServer implementation This is the core implementation of the "plugin server" that will support the API described at https://docs.google.com/document/d/1T8P323DJxsc3YPzveNIaSKWFkrJp9ydTR4jp_XFb7XQ/edit?resourcekey=0-f8Ue29KMUizqXNGhATp1tg#heading=h.23fjh5hfm2is This is heavily curbed from the ServerPlugin class at `package:analyzer_plugin/plugin/plugin.dart`, but does not depend on it. It depends on two concepts from the analyzer_plugin package: (1) the protocol used for de/serializing requests, responses, etc. And (2) the `PluginCommunicationChannel` class. This is also just a utility for communicating between the analysis server and the plugin server. This plugin server is capable of "registering" individual "plugins", which allows plugins to register individual (maybe multiple) lint rules, and individual (maybe multiple) quick fixes. The plugin server for now only responds essentially to three requests: * `ANALYSIS_REQUEST_SET_CONTEXT_ROOTS` * `EDIT_REQUEST_GET_FIXES` * `PLUGIN_REQUEST_VERSION_CHECK` All files are analyzed during `handleAnalysisSetContextRoots`, and quick fixes are calculated during `handleEditGetFixes`. There are many TODOs, but the included test shows that this plugin server can notify the analysis server of lint diagnostics to be reported, and can respond to a query for quick fixes. Change-Id: Ibc93332319220a2caf49d20ab480940041a15049 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/382480 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: 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.