Files

T

Konstantin Shcheglov 3428cc6dae Add AnalysisDriver.resetUriResolution() and use it for analysis.reanalyze request.

This CL changes "analysis.reanalyze" API. We decided to repurpose it. It was not
used for some time now in IntelliJ, and AFAIK has never been used in VS Code.

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

Change-Id: I7510b0189197c9f3f848b0fc59a7b2bd22889ac7
Reviewed-on: https://dart-review.googlesource.com/c/85523
Reviewed-by: Paul Berry <paulberry@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>

2018-11-29 19:08:30 +00:00

benchmark

Remove CFE integration from analyzer, analysis_server, and analyzer_cli.

2018-08-29 13:46:45 +00:00

bin

Normalize with the internal verison of this file.

2018-09-04 16:19:45 +00:00

doc

Add AnalysisDriver.resetUriResolution() and use it for analysis.reanalyze request.

2018-11-29 19:08:30 +00:00

lib

Add AnalysisDriver.resetUriResolution() and use it for analysis.reanalyze request.

2018-11-29 19:08:30 +00:00

test

Add AnalysisDriver.resetUriResolution() and use it for analysis.reanalyze request.

2018-11-29 19:08:30 +00:00

tool

Add AnalysisDriver.resetUriResolution() and use it for analysis.reanalyze request.

2018-11-29 19:08:30 +00:00

analysis_options.yaml

Update analysis options files.

2018-07-03 00:20:06 +00:00

AUTHORS

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

2015-05-08 20:57:44 +00: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

Update synced version of pkg:test

2018-10-16 16:12:38 +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.