Files

T

Danny Tuppeny c5bfccc6fb Make downloading the LSP spec a flag and commit the version parsed locally

Change-Id: Ib46be800dcfe3369bcc9a222d1097ae4a0efdff6

Ensure licence/attribution is included in our copy of the spec

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

2019-01-16 17:20:54 +00:00

benchmark

Clean up the remaining copyright notices in analysis_server

2019-01-11 15:38:56 +00:00

bin

Clean up the remaining copyright notices in analysis_server

2019-01-11 15:38:56 +00:00

doc

Add optional elementUri field to CompletionSuggestion types in analysis server protocol

2019-01-09 00:13:39 +00:00

lib

Fix LSP exceptions serializing ResponseErrors with Uris

2019-01-16 16:57:43 +00:00

test

Fix LSP exceptions serializing ResponseErrors with Uris

2019-01-16 16:57:43 +00:00

tool

Make downloading the LSP spec a flag and commit the version parsed locally

2019-01-16 17:20:54 +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

…

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.