Brian Wilkerson
174759cfbd
Several of the lint rules have been producing diagnostics with more than one lint code, but the code that deserializes diagnostics has only been able to use one of the codes. That potentially leads to errors, though I suspect the bug has been invisible because we serialize and deserialize the messages. Nevertheless, it seems like we ought to do this correctly and that it will eventually lead to a visible bug. Change-Id: I41faaa45df63cb3c74042661e1c89e3fde3d72d0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/154843 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.