Files

T

Mike Fairhurst 985160c08d Replace making getInnermostContext public with making a getFolder method

This way SingleContextManager can fulfill the interface too (it can't
provide a ContextInfo, and the concept of `innermost` doesn't really
exist).

BUG=
R=brianwilkerson@google.com

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

2017-03-14 16:13:16 -07:00

benchmark

Remove unused import

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

bin

…

doc

CompletionSuggestion API for arg list text ranges.

2017-03-01 16:10:46 -08:00

lib

Replace making getInnermostContext public with making a getFolder method

2017-03-14 16:13:16 -07:00

test

Add an object that can manage which plugins are associated with each context / driver

2017-03-14 12:09:53 -07:00

tool

Move some of analyzer's code generation utilities into front_end.

2017-03-14 12:30:18 -07:00

.analysis_options

Mark analysis_server as being strong-mode clean

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

analysis_server.iml

Fix analysis_server.iml file to account for newly created directories.

2017-02-15 13:07:59 -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

Update the contributing file for the analysis server.

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

LICENSE

…

pubspec.yaml

Switch to using expectAsync0() to address some deprecation warnings.

2017-02-17 09:39:23 -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.