dart-sdk/pkg/analysis_server
Ahmed Ashour 3c10e484c9 Flutter Widget Key to be nullable
Fixes #46913

Change-Id: Id2d72ce497eaa1512c2bb95f023c9ff0160c5005
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/210128
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
2022-05-11 19:20:24 +00:00
..
benchmark [analysis_server] Add shared protocol.dart file for LSP 2022-05-11 15:28:35 +00:00
bin [analysis_server] re-enble null safety for the analysis server entrypoint 2021-05-13 17:18:15 +00:00
doc Switch to protocol version 1.33.0, enable new completion protocol. 2022-03-29 20:53:39 +00:00
lib [analysis_server] Rename some LSP spec classes to match upcoming JSON models 2022-05-11 19:06:04 +00:00
test Flutter Widget Key to be nullable 2022-05-11 19:20:24 +00:00
tool [analysis_server] Rename some LSP spec classes to match upcoming JSON models 2022-05-11 19:06:04 +00:00
analysis_options.yaml analyzer: Prefer string interpolations 2022-05-04 20:45:25 +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 Add a progress bar to completion_metrics 2022-04-19 20:40:19 +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.