Paul Berry
527dd5a99f
This paves the way for a follow-up CL that will standardize all diagnostic names to `lower_snake_case` conventions. For now, the case differences between the entries in `error_fix_status.yaml` and the actual diagnostic code names are accounted for by adding some calls to `.toLowerCase()` to `verify_error_fix_status.dart`. Change-Id: I6a6a6964b0eacf50b11f302ab511fba149b1ac07 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/465981 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.