Files

T

P.Y. Laligand ce79a77331 Remove Fuchsia-specific build files.

Also fix Fuchsia tools to account for new project location (//third_party/dart).

Change-Id: If89a934729c4fa44229eaca83219dbdf8bb700a8
Bug:
Reviewed-on: https://dart-review.googlesource.com/14800
Commit-Queue: Zach Anderson <zra@google.com>
Reviewed-by: Zach Anderson <zra@google.com>

2017-10-19 17:52:37 +00:00

benchmark

Type return Future for AnalysisServer integration tests send().

2017-09-06 16:07:49 +00:00

bin

…

doc

Add two new element types to the protocol.

2017-10-18 19:02:47 +00:00

lib

Send test element kinds for test outline items.

2017-10-11 17:00:41 +00:00

test

Add two new element types to the protocol.

2017-10-18 19:02:47 +00:00

tool

Add two new element types to the protocol.

2017-10-18 19:02:47 +00:00

analysis_options.yaml

Restore partial analysis of analysis options files

2017-06-22 08:00:50 -07:00

AUTHORS

…

CHANGELOG.md

…

CONTRIBUTING.md

Update the contributing file for the analysis server.

2017-02-08 08:13:20 -08:00

LICENSE

…

pubspec.yaml

Bump the version of intl used by analysis-server.

2017-10-16 20:09:57 +00:00

README.md

Update the analysis server diagnostic page - re-enable code completion and overlay pages,

2017-05-30 18:46:33 -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.