languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-16 05:07:52 +00:00
Code Issues Packages Projects Releases Wiki Activity
dart-sdk/pkg/analysis_server
History
Brian Wilkerson 07db94d454 Add support for details and implement some initial details for regions 
Details provide a way for clients to provide navigation support. I'm
imagining that the description could be used as link text.

The deatils are currently more of a data dump than information. I need
to see more migration results in order to figure out when and how to
pare down the data into actionable information.

We might want to capture all of the navigation targets as we build the
info so that we can create anchors in the HTML.

Change-Id: Ie48622ce7d935d3c028ea42e51cfc8da590db149
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/118908
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
Reviewed-by: Samuel Rawlins <srawlins@google.com>
2019-09-26 18:03:40 +00:00
..
benchmark [analysis_server] Fix flaky hanging in analysis server benchmark 2019-08-01 16:30:13 +00:00
bin Clean up the remaining copyright notices in analysis_server 2019-01-11 15:38:56 +00:00
doc Protocol for 'server.log' notification. 2019-08-29 22:33:33 +00:00
lib Add support for details and implement some initial details for regions 2019-09-26 18:03:40 +00:00
test Add support for details and implement some initial details for regions 2019-09-26 18:03:40 +00:00
tool Add output directory field to dartfix API 2019-09-16 22:51:21 +00:00
analysis_options.yaml Enable pedantic 1.8.0 in analyzer, analysis_server 2019-09-25 19:08:03 +00:00
AUTHORS
CHANGELOG.md
CONTRIBUTING.md Update the contributing file for the analysis server. 2017-02-08 08:13:20 -08:00
LICENSE
pubspec.yaml Enable pedantic 1.8.0 in analyzer, analysis_server 2019-09-25 19:08:03 +00:00
README.md Add some notes on using Dart LSP with Vim 2019-02-27 12:08:32 +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 original protocol is specified in the file analysis_server/doc/api.html and (less complete) Language Server Protocol support is documented in tool/lsp_spec/README.md.

Features and bugs

Please file feature requests and bugs at the issue tracker.