Paul Berry
2b5e655c34
Changes the test logic in `analysis_server` and `analyzer_testing` so that after printing `To accept the current state, expect:`, it prints diagnostic codes in their proper camelCase format. Also removes some bogus code from `pkg/analyzer_testing/lib/analysis_rule/analysis_rule.dart` that erroneously suggested passing a `name:` parameter to the top level `error` function. This function does not accept any parameter called `name`. Previously, only tests in `pkg/analyzer/test` printed the diagnostic codes correctly. Fixes https://github.com/dart-lang/sdk/issues/62651. Change-Id: I6a6a6964b17cf798c1355e09f9a4633e1fbe388c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/480041 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: 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.