Files

T

Paul Berry 717da6731b Eliminate Modifier.TYPEDEF and deprecate ClassElement.isTypedef.

Modifier.TYPEDEF was redundant with Modifier.MIXIN_APPLICATION and
ClassElement.isTypedef was redundant with
ClassElement.isMixinApplication.

Since Modifier.TYPEDEF was private to analyzer, it has been
eliminated.  Since ClassElement.isTypedef is part of the public API to
analyzer, it is retained, but with a "@deprecated" annotation.

R=scheglov@google.com

Review URL: https://codereview.chromium.org//1158193008

2015-06-01 14:17:40 -07:00

bin

Server clean-up

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

doc

Add lineLength parameter to edit.format request (issue 23519)

2015-06-01 09:39:02 -07:00

lib

Eliminate Modifier.TYPEDEF and deprecate ClassElement.isTypedef.

2015-06-01 14:17:40 -07:00

test

Issue 23409. Don't set 'propagatedType' in (vs. after) 'name is Type'.

2015-06-01 12:40:30 -07:00

tool/spec

Add lineLength parameter to edit.format request (issue 23519)

2015-06-01 09:39:02 -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

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

2015-05-08 20:57:44 +00:00

LICENSE

Logging support for server

2014-01-17 16:52:25 +00:00

pubspec.yaml

Issue 23409. Don't set 'propagatedType' in (vs. after) 'name is Type'.

2015-06-01 12:40:30 -07:00

README.md

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

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