Files

T

Konstantin Shcheglov 33ecec5d4f Replace expect() with outOfTestExpect() in Analysis Server performance benchmark.

In package:test function expect() does not want to be used outside of
test() methods. So, we need a partial copy for using it in integration
tesitng code, and performance benchmarks.

R=paulberry@google.com, brianwilkerson@google.com
BUG=

Review URL: https://codereview.chromium.org/2413573003 .

2016-10-12 12:57:03 -07:00

benchmark

Replace expect() with outOfTestExpect() in Analysis Server performance benchmark.

2016-10-12 12:57:03 -07:00

bin

…

doc

Improve server documentation

2016-10-06 14:57:10 -07:00

lib

Fix exception in checked mode

2016-10-11 17:30:16 -07:00

test

Replace expect() with outOfTestExpect() in Analysis Server performance benchmark.

2016-10-12 12:57:03 -07:00

tool

Replace expect() with outOfTestExpect() in Analysis Server performance benchmark.

2016-10-12 12:57:03 -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

BUILD.gn

Added build files for the analyzer and analysis_server packages.

2016-10-06 14:00:19 -07: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

…

pubspec.yaml

Move analysis_server dependency on analyzer back to 0.28.0

2016-10-06 20:38:35 -07:00

README.md

Add a link to API spec (#27158 )

2016-08-25 11:04:35 -07:00

README.md

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.