Brian Wilkerson
d85ab6df0c
There are no functional changes, just changes to the way the logging functionality is implemented. The motivation for the changes is to allow future CLs to explore ways of changing the expectations so that async handling of messages won't produce flaky tests. All references to the 'messageLog' outside the class have been replaced by higher-level methods with a semantic meaning. The class has been split into an interface and an implementation, which allows the test-specific aspects to be in the `test` directory. Some additional code cleanup was also done. Change-Id: Ie515f71153a96fb6e92eb8e2eb05f4b5e064bbd7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/421965 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Phil Quitslund <pquitslund@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.