Danny Tuppeny
0647d9a228
* Tweak comment that was based on integration test verison. See #30285 * Include additional 1/2-line spans that end on same lines as >2 line spans. See #30285 * Add tests to ensure no unwanted closing labels from multiline expressions. See #30285 * Don't show closing labels for code inside interpolated strings. See #30285 * Remove unwanted @soloTest. See #30285 * Make casing of test names consistent. See #30285 * Add a constructor and make fields final. See #30285 * Use putIfAbsent for adding to map. See #30285 * Shorten closing labels constructor. See #30285 * Run "Sort members" on closing labels files. See #30285 * Remove unnecessary type annotations. See #30285
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
protocol is specified in the file analysis_server/doc/api.html.
Features and bugs
Please file feature requests and bugs at the issue tracker.