dart-sdk/pkg/analysis_server
Konstantin Shcheglov 9696c9dcd0 Change analysis_server tests to use /project/test.dart as the test file.
Correspondingly all files that were referenced using relative URI(s)
also put into /project, which is the contextRoot for the test
AnalysisDriver.

This will let us (in a following CL) start checking that the element
being renamed is defined inside the current workspace (the set of
analysis roots). Currently the context root is hardcoded as /project.

R=brianwilkerson@google.com

Change-Id: I9dca3509af1be13c9016bf03d4a4b95d71bc9374
Reviewed-on: https://dart-review.googlesource.com/56031
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
2018-05-22 00:31:22 +00:00
..
benchmark Fix constant-related deprecation warnings in analyzer packages 2018-05-17 21:24:38 +00:00
bin
doc Update FoldingKinds enum, update specs and increase version number 2018-05-14 16:48:48 +00:00
lib Give (the old) ContextRoot path.Context to work with paths. 2018-05-21 22:04:24 +00:00
test Change analysis_server tests to use /project/test.dart as the test file. 2018-05-22 00:31:22 +00:00
tool Fix constant-related deprecation warnings in analyzer packages 2018-05-17 21:24:38 +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 Upgrade the dep on package:isolate. 2018-04-16 17:08:48 +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

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.