Brian Wilkerson
680e109ad2
The code is now gathering both element and token data in several places where it used to gather only one of the two (using a new utility method). The metrics are now better labeled to make the output easier to read. It's also gathering a new metric: the distance between the static type of a target and the class in which a referenced member is declared. Change-Id: I566c02b069749221983ec960b8a67b293052bd93 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/135400 Reviewed-by: Jaime Wren <jwren@google.com> Reviewed-by: Phil Quitslund <pquitslund@google.com> Commit-Queue: 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 (less complete) 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.