Files

T

Konstantin Shcheglov d29ba1e238 Store exceptions with transitive files context into ByteStore.

The key under which the exception context is stored, is included into
ExceptionResult, so Analysis Server can include the key into the message.

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

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

2017-01-30 12:57:44 -08:00

benchmark

Remove unused import

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

bin

…

doc

Regen the analysis server spec to include the diagnostic domain.

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

lib

Store exceptions with transitive files context into ByteStore.

2017-01-30 12:57:44 -08:00

test

ContextBuilder should to throw when a root folder does not exist.

2017-01-29 09:37:24 -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

…

BUILD.gn

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

2016-12-09 21:52:32 -08:00

CHANGELOG.md

…

CONTRIBUTING.md

…

LICENSE

…

pubspec.yaml

use latest pkg/isolate

2017-01-28 13:53:17 -08: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.