Sam Rawlins
8aa0bf58ab
These utilities are distinct from the base classes like AnalysisRule and LinterContext. And their import requirements are also distinct. Separating them in the filesystem should simplify how we slice up the public API. Change-Id: I365c48c41e5d3db1e3aa649fd70b94cd7da1b069 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/395561 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.