languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-15 21:10:22 +00:00
Code Issues Packages Projects Releases Wiki Activity
dart-sdk/pkg/analysis_server
History
Konstantin Shcheglov 9f35115b90 Use FooImpl in BarImpl getters/setters, property related. 
I think we might get away with this now, because we don't let users
create elements manually.

Presubmit in google3 looks green.
https://fusion2.corp.google.com/presubmit/tap/483535261/OCL:483535261:BASE:483575659:1666678949553:5d26313d/targets

Change-Id: Id9618e2d8a15ab98c5919750461c508e87f76c7b
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/265405
Reviewed-by: Samuel Rawlins <srawlins@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
2022-10-26 03:49:43 +00:00
..
benchmark Add more await or unawaited() to DAS. 2022-07-12 00:59:01 +00:00
bin [analysis_server] re-enble null safety for the analysis server entrypoint 2021-05-13 17:18:15 +00:00
doc Remove domain 'kythe' from DAS. 2022-10-21 17:03:29 +00:00
lib Use FooImpl in BarImpl getters/setters, property related. 2022-10-26 03:49:43 +00:00
test [analysis_server] Handle type arguments on named type references for initial Call Hierarchy item 2022-10-25 16:31:10 +00:00
tool [analysis_server] Include type arguments in Type Hierarchy 2022-10-25 16:00:41 +00:00
analysis_options.yaml [analysis_server] Enable unawaited_futures lint and fix remaining violations 2022-07-13 18:40:53 +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] Remove string_scanner dependency from TestCode 2022-10-19 16:28:25 +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.