mirror of
https://github.com/dart-lang/sdk
synced 2024-09-15 23:29:47 +00:00
8f48cbcccb
This is the first of many such CLs. We need to record the completion everywhere that `OpType` is computing it in order to eventually be able to stop using `OpType`. I have temporary code that compares the two computations in order to ensure that they're the same, but I can't commit it into prod, nor will it be useful beyond this transition. In addition to recording the completion location in more places, this also better handles the case when the offset is immediately before the first character of a top-level declaration. I believe that we need to do something similar when immedately after the last character, when before and after class members, and when before an after statements. Change-Id: I046675c56243981762cd06db4cd35c17989ccf27 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/348762 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Samuel Rawlins <srawlins@google.com> |
||
---|---|---|
.. | ||
benchmark | ||
bin | ||
doc | ||
lib | ||
test | ||
tool | ||
analysis_options.yaml | ||
AUTHORS | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
OWNERS | ||
pubspec.yaml | ||
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 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.