Michal Terepeta
97093b2594
This introduces a way to see what paths have been searched for by the `BazelWorkspace` and adds a polling-based watcher to detect when files generated by Bazel appear (or have changed). This allows us to re-analyze things automatically instead of, e.g., restarting the server. Change-Id: I60eae29b0e4fcc3a91d8d2275c6898e45548ea03 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/168649 Commit-Queue: Michal Terepeta <michalt@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@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.