dart-sdk/pkg/analysis_server
2015-11-23 12:09:52 -05:00
..
benchmark refactor timing tests to not use the test framework 2015-10-19 16:34:56 -07:00
bin Server clean-up 2015-01-12 17:34:14 +00:00
doc Experimental getDiagnostics request (#24480). 2015-11-05 15:05:21 -08:00
lib general completion contributor cleanup 2015-11-23 11:03:01 -05:00
test (TBR) fix completion test 2015-11-23 12:09:52 -05:00
tool/spec Rolling average work queue diagnostic (#24933). 2015-11-20 14:24:47 -08:00
AUTHORS pkg/analysis_server: don't explicitly import matcher - use exports from unittest 2015-05-08 20:57:44 +00:00
CHANGELOG.md pkg/analysis_server: don't explicitly import matcher - use exports from unittest 2015-05-08 20:57:44 +00:00
CONTRIBUTING.md pkg/analysis_server: don't explicitly import matcher - use exports from unittest 2015-05-08 20:57:44 +00:00
LICENSE Logging support for server 2014-01-17 16:52:25 +00:00
pubspec.yaml Analyzer version bump. 2015-11-20 16:40:36 -08:00
README.md pkg/analysis_server: don't explicitly import matcher - use exports from unittest 2015-05-08 20:57:44 +00:00

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.