dart-sdk/pkg/analysis_server
Brian Wilkerson 8f48cbcccb Record the completion location in more places
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>
2024-01-26 21:17:19 +00:00
..
benchmark Remove support for the older legacy completion protocol 2023-12-12 00:54:48 +00:00
bin [analysis_server] re-enble null safety for the analysis server entrypoint 2021-05-13 17:18:15 +00:00
doc Remove support for the older legacy completion protocol 2023-12-12 00:54:48 +00:00
lib Record the completion location in more places 2024-01-26 21:17:19 +00:00
test Record the completion location in more places 2024-01-26 21:17:19 +00:00
tool [analysis_server] Add experimental TextDocumentContentProvider support for virtual documents 2024-01-18 17:34:43 +00:00
analysis_options.yaml enable flutter_style_todos in server 2023-11-14 21:08:12 +00:00
AUTHORS
CHANGELOG.md
CONTRIBUTING.md
LICENSE Update LICENSE 2021-04-07 10:28:38 +00:00
OWNERS [infra] Add OWNERS to the Dart SDK 2022-02-14 14:06:34 +00:00
pubspec.yaml [analysis_server] Resolve TODO in convert_to_switch_expression quick assist 2023-11-17 22:53:26 +00:00
README.md "master->main" migration 2021-09-09 18:14:36 +00:00

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.