Sam Rawlins
f6828ddd8d
Just a lot of tidying in preparation for this code being public API in the `analysis_server_plugin` package. A big change: * Convert `CorrectionProducer.assistArguments`, `CorrectionProducer.fixArguments`, and `CorrectionProducer.multiFixArguments` each from a `List<Object>?` to a `List<String>?`. This should be a no-op. Smaller changes: * Make private: `AssistProcessor.generators`, `.multiGenerators`, `.assistContext`, `.assists`, * Make private: `CorrectionProducerContext.selectionOffset`, `.selectionLength`, `.utils`, `.sessionHelper`, `.unitResult`, `.applyingBulkFixes`, `.diagnostic`, `.node`, `.token`. * Make private: `FixProcessor.fixContext`. * Remove `CorrectionProducerContext.selectionEnd`, `.unit`, `.file`, `.session`, `.workspace`, `.typeProvider`; these can be accessed via getters. * Remove unused `FixProcessor.computeFix()`. * Make doc comments more idiomatic. Change-Id: I100fe81aad612967191568fe207ff0b807f131b3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/364420 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@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.