In addition to implementing the feature, this CL updates one of the contributors to use the new feature as a way of testing it. I haven't looked to see whether it impacts the metrics, but I wouldn't expect much change anyway because of the small number of completions that are likely to be effected by this change. It might be interesting to start thinking about ways to measure the impact of individual features. Change-Id: Idd0040a774e5fd9a6e3f6c29d0aa7fd762676fbe Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/143622 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Jaime Wren <jwren@google.com>
analyzer_plugin
A framework for building plugins for the analysis server.
Usage
Note: The plugin support is not currently available for general use.
Plugins are written in Dart and are run in the same VM as the analysis server. The analysis server runs each plugin in a separate isolate and communicates with the plugin using a plugin API. This API is similar to the API used by the analysis server to communicate with clients.
Plugins are automatically discovered and run by the analysis server.
This package contains support code to make it easier to write a plugin. There is a tutorial describing how to use the support in this package.
Support
Post issues and feature requests on the issue tracker.
Questions and discussions are welcome at the Dart Analyzer Discussion Group.
License
See the LICENSE file.