Files

T

Danny Tuppeny 8ae255d876 Improve regex for extracting request constants from LSP spec

Some requests have additional newlines, so this change allows any number instead of exactly one.

Change-Id: Ie32b525b9b834223f91cd6339f6932fb02007c78
Reviewed-on: https://dart-review.googlesource.com/c/87060
Auto-Submit: Danny Tuppeny <dantup@google.com>
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>

2018-12-12 15:00:22 +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

Re-apply "Add AnalysisDriver.resetUriResolution() and use it for analysis.reanalyze request."

2018-12-06 23:14:28 +00:00

lib

Improve regex for extracting request constants from LSP spec

2018-12-12 15:00:22 +00:00

test

fix options integration tests

2018-12-12 00:28:39 +00:00

tool

Improve regex for extracting request constants from LSP spec

2018-12-12 15:00:22 +00:00

analysis_options.yaml

Update analysis options files.

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

AUTHORS

…

CHANGELOG.md

…

CONTRIBUTING.md

…

LICENSE

…

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.