Files

T

Janice Collins ace1d9b921 Do not repeatedly analyze a full library per part when dartfixing.

Migration performance improves 10x on web_ui with this CL.
Also fixes a heisenbug in the linter code where identical uniqueNames
for LintCodes could wind up in objects that compare differently.

Bug: https://github.com/dart-lang/sdk/issues/40915
Change-Id: Iddddfd7659f4bc724ddf21ebae41750a0ee51e74
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/138940
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Janice Collins <jcollins@google.com>

2020-03-10 21:16:11 +00:00

benchmark

Start converting dartdoc style in analysis_server

2020-02-13 15:00:03 +00:00

bin

Start converting dartdoc style in analysis_server

2020-02-13 15:00:03 +00:00

doc

Mark the completion.registerLibraryPaths as deprecated in the Dart Analysis Server.

2019-11-21 22:16:38 +00:00

lib

Do not repeatedly analyze a full library per part when dartfixing.

2020-03-10 21:16:11 +00:00

test

Add additional metrics into the completion metrics algorithm, MRR broken apart by type member completions, and non-type member completions

2020-03-10 19:48:21 +00:00

tool

Add additional metrics into the completion metrics algorithm, MRR broken apart by type member completions, and non-type member completions

2020-03-10 19:48:21 +00:00

.gitignore

[migration tool] convert the javascript code in the migration tool to dart

2020-02-04 21:46:08 +00:00

analysis_options.yaml

Enable slash_for_doc_comments in analysis_server

2020-02-14 17:17:17 +00:00

AUTHORS

…

CHANGELOG.md

…

CONTRIBUTING.md

…

LICENSE

…

pubspec.yaml

[nnbd preview] iteration on the nnbd preview tool ui; fix layout and scrolling

2020-02-07 23:52:00 +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.