mirror of
https://github.com/dart-lang/sdk
synced 2024-11-02 12:24:24 +00:00
6872a0bb77
Both LSP and legacy server tests had their own implementation of writing package_config files. This combines them by moving the LSP `ConfigurationFilesMixin` mixin to its own file and updating the legacy test classes to use it. This removes a little duplication and avoids adding more for the temporary packages required for Macros that's currently only in the LSP version (but required for some upcoming LSP-over-Legacy tests). Change-Id: Iaa4055c544df4cdd5a0f140b0c6171ff1a406946 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/347081 Reviewed-by: Phil Quitslund <pquitslund@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> |
||
---|---|---|
.. | ||
benchmark | ||
bin | ||
doc | ||
lib | ||
test | ||
tool | ||
analysis_options.yaml | ||
AUTHORS | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
OWNERS | ||
pubspec.yaml | ||
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.