Paul Berry
a74253987b
This establishes the base functionality. A lot of follow-up work is needed from here: - Each trace should have an entry at the top of it pointing to the thing that was made nullable. - The source code links in traces don't include lengths, so we can't highlight whole identifiers when the user clicks on a link. - Description strings are currently generated by running toString() on the individual nullability nodes and edges, resulting in long-winded and useless descriptions. Change-Id: Ibb370bae6bedc7a8c86092462785023002a48ac3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/138481 Reviewed-by: Samuel Rawlins <srawlins@google.com> Commit-Queue: Paul Berry <paulberry@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.