Sam Rawlins
fd4602f019
We also stop reporting `HintCode.DEPRECATED_MEMBER_USE_FROM_SAME_PACKAGE` and `HintCode.DEPRECATED_MEMBER_USE_FROM_SAME_PACKAGE_WITH_MESSAGE` as these are now replaced by the new lint rule. The biggest change here is in the DEPRECATED_MEMBER_USE tests, as most of these tests have `DEPRECATED_MEMBER_USE_FROM_SAME_PACKAGE` reported (since it's easier to write tests with files in one package). We move all of those tests to `DEPRECATED_MEMBER_USE` tests, without losing coverage. Bug: https://github.com/dart-lang/sdk/issues/50796 Change-Id: I7cada44265cd0e1e47ab77d4354de9a5571db614 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/289444 Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Kevin Moore <kevmoo@google.com> Reviewed-by: Nate Bosch <nbosch@google.com>
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.