Files

T

Brian Wilkerson d1689fe748 Fix a RangeError in LSP completions

I have not been able to reproduce this bug in a test, but it seems
obvious when looking at the code what the issue is.

Change-Id: I45a5cdb9c8f31391e26bfaa6490bc20877f545d8
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/136853
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>

2020-02-25 18:46:01 +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

Fix a RangeError in LSP completions

2020-02-25 18:46:01 +00:00

test

Revert "Issue 37487. Add CompilationUnit.languageVersion override."

2020-02-25 04:39:10 +00:00

tool

Stop producing trailing spaces when writing the last column of tabular data

2020-02-20 01:57:45 +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.