dart-sdk/pkg/analysis_server
2016-08-04 11:28:16 -07:00
..
benchmark Don't run Analysis Server performance tests in checked mode. 2016-07-15 09:05:09 -07:00
bin Server clean-up 2015-01-12 17:34:14 +00:00
doc Adds PID to server.connected notification (#26744). 2016-06-21 16:00:27 -07:00
lib Convert server and cli and deprecate the old implementation 2016-08-04 11:28:16 -07:00
test Convert server and cli and deprecate the old implementation 2016-08-04 11:28:16 -07:00
tool/spec Adds PID to server.connected notification (#26744). 2016-06-21 16:00:27 -07:00
.analysis_options Mark analysis_server as being strong-mode clean 2016-08-01 12:23:22 -07: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 Update dependency on pkg/package_compiler 2016-07-27 08:42:05 -07: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.