Brian Wilkerson
4e9a98bb45
This also contains a few minor clean-up changes to the parser, mostly dealing with keys that should have been required but weren't. I'm tempted to make the date a required field and then use it to sort the transforms so that they are applied from oldest to newest. Right now it's optional but provides a way for users to document the date for their own record keeping. Thoughts appreciated. Change-Id: If3a22bbc2dea30f760f868c1ca1bf41aaf4654c9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/162382 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.