Files

T

Leaf Petersen 83fc4b6b46 Put a TypeProvider on the TypeSystem implementations.

Adding a TypeProvider instance to TypeSystem to avoid needing to
thread it through the various APIs, and to avoid having to change
the API every time a method which previously did not need to
access the TypeSystem suddenly does.

BUG=
R=jmesserly@google.com

Review-Url: https://codereview.chromium.org/2590883004 .

2017-01-09 02:40:10 -08:00

benchmark

Remove unused import

2016-12-04 16:03:47 -08:00

bin

Server clean-up

2015-01-12 17:34:14 +00:00

doc

Regen the analysis server spec to include the diagnostic domain.

2016-11-20 10:27:58 -08:00

lib

Put a TypeProvider on the TypeSystem implementations.

2017-01-09 02:40:10 -08:00

test

Fix the rest of the completion tests with the new analysis driver.

2017-01-08 15:16:33 -08:00

tool

Regen the analysis server spec to include the diagnostic domain.

2016-11-20 10:27:58 -08:00

.analysis_options

Mark analysis_server as being strong-mode clean

2016-08-01 12:23:22 -07:00

.gitignore

Add a gitignore file for the analysis_server package.

2016-11-20 10:05:11 -08:00

AUTHORS

pkg/analysis_server: don't explicitly import matcher - use exports from unittest

2015-05-08 20:57:44 +00:00

BUILD.gn

Use the new path to the linter package (#28062 )

2016-12-09 21:52:32 -08: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.