Sam Rawlins
5f19f0edca
This has a few nice follow-on benefits: * SnippetProducer no longer needs to rely on LinterContext. * Many classes no longer need a PathContext passed around, or a `String content`. * BestPracticesVerifier has _3 fewer parameters_, and 1 fewer field. * `_InvalidAccessVerifier._isInTestDirectory` no longer needs to be `late`. Change-Id: I0c2059feae22a75f7c706676cc228fa404dd0cf7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/365300 Reviewed-by: Phil Quitslund <pquitslund@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.