languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-19 14:32:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
dart-sdk/pkg/analysis_server
History
Brian Wilkerson c42ab25787 Refactor TestCode to prepare to move it to analyzer 
This is the first phase of preparing it to be moved. The plan is for the
extensions to remain in this library along with an export of the new
library in the analyzer package.

The second phase will be to rewrite it to not use string_scanner so that
we don't have to add a dependency to the analyzer package.

Change-Id: I0d4e9c47bdcb7b825a9d3bfc76331a4e575ac664
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/263443
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
2022-10-18 18:31:53 +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 Add some initial documentation related to navigation 2022-09-16 22:04:40 +00:00
lib [analysis_server] Prevent convert method<->getter refactors on SDK/external package files 2022-10-18 16:24:16 +00:00
test Refactor TestCode to prepare to move it to analyzer 2022-10-18 18:31:53 +00:00
tool Deprecate 'DartType.element2' use 'element' instead. 2022-10-05 16:30:09 +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] Add a new mechanism for marking up test code with regions/positions 2022-09-22 16:33:18 +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.