Sam Rawlins
26102c5d52
This renames the old screen, "Legacy plugins" and adds a new screen, "Plugins". On the new plugins screen, we ask the plugins isolate(s) for their plugins details, and print the following, for eadh plugin: * the plugin's name * the names of the registered lint rules * the names of the registered warning rules * the IDs and "messages" of the registered assists * the IDs and "messages" and associated diagnostic codes of the registered quick fixes More to come in follow ups: * The resolved versions of plugin packages (coming from package_config.json) Change-Id: Ic3dc4c5bffa64fd4da4097c042a847cc064e41ce Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/447763 Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
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.