Sam Rawlins
92bebe661b
This data is collected on shutdown, the same as the legacy analytics data. This is implementation for some of the analytics we want to collect, specified at go/dart-analyzer-plugin-analytics. * How many plugins are enabled for each context? * How many lint rules are registered for each plugin? * How many warning rules are registered for each plugin? * How many fixes are registered for each plugin? * How many assists are registered for each plugin? Change-Id: I36c176737c194550e1947985576ed461fd8a1bf3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/452482 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@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.