Brian Wilkerson
07db94d454
Details provide a way for clients to provide navigation support. I'm imagining that the description could be used as link text. The deatils are currently more of a data dump than information. I need to see more migration results in order to figure out when and how to pare down the data into actionable information. We might want to capture all of the navigation targets as we build the info so that we can create anchors in the HTML. Change-Id: Ie48622ce7d935d3c028ea42e51cfc8da590db149 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/118908 Commit-Queue: 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 (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.