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>
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
original protocol is specified in the file analysis_server/doc/api.html
and Language Server Protocol support is documented in
tool/lsp_spec/README.md.
Features and bugs
Please file feature requests and bugs at the issue tracker.