Files

T

Konstantin Shcheglov 07367d05cd Basic implementation of FlutterOutlineComputer.

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

Change-Id: I22c96c2a35c086814aace13f0121cc0361f3386f
Reviewed-on: https://dart-review.googlesource.com/36140
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>

2018-01-21 18:12:58 +00:00

benchmark

Create the new flag --use-cfe in the analyzer, analysis server and analyzer_cli and migrate the old behavior of --preview-dart-2 to --use-cfe. The --preview-dart-2 flag is now a no-op, with functionality coming soon.

2018-01-08 22:37:05 +00:00

bin

Server clean-up

2015-01-12 17:34:14 +00:00

doc

Add basic Flutter outline subscription/notification to the protocol.

2018-01-19 23:22:17 +00:00

lib

Basic implementation of FlutterOutlineComputer.

2018-01-21 18:12:58 +00:00

test

Basic implementation of FlutterOutlineComputer.

2018-01-21 18:12:58 +00:00

tool

Add basic Flutter outline subscription/notification to the protocol.

2018-01-19 23:22:17 +00:00

analysis_options.yaml

Restore partial analysis of analysis options files

2017-06-22 08:00:50 -07: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 args deps in analysis_server pubspec

2018-01-18 22:16:44 +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.