Brian Wilkerson
00e4d8f33d
This adds support so that tests of lint-based quick fix tests can use the output of the linter rather than cons-ing up a fake lint to drive the test. It also converts many of the existing tests to use real lints. There were/are an amazing number of tests that were invalid and needed to be fixed. This includes fixes for some of them, but there are still several tests that have not been converted because they fail when run using the output of the linter. Some of these are invalid tests, but some might indicate bugs in the quick fix generation that should be fixed. Change-Id: Iea806849ea111dc8454073e8fe44fd42c5208652 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/134141 Reviewed-by: Phil Quitslund <pquitslund@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@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.