languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-07-19 20:17:27 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
dart-sdk/pkg/analysis_server
History
Konstantin Shcheglov 473ba0254c Legacy. Use non-nullable TypeProvider, don't create legacy TypeProvider/TypeSystem. 
Change-Id: I01ec3849ed0ad1f2a777cd14a51720b88c489a37
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/350003
Reviewed-by: Phil Quitslund <pquitslund@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
2024-02-03 01:22:50 +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 [analysis_server] Add a supportsUris client capability for legacy server to switch into URI mode 2024-02-01 22:19:00 +00:00
lib Legacy. Use non-nullable TypeProvider, don't create legacy TypeProvider/TypeSystem. 2024-02-03 01:22:50 +00:00
test Legacy. Use non-nullable TypeProvider, don't create legacy TypeProvider/TypeSystem. 2024-02-03 01:22:50 +00:00
tool [analysis_server] Add a supportsUris client capability for legacy server to switch into URI mode 2024-02-01 22:19:00 +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

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.