![]() Originally we didn't use the LSP Request/Response classes, and just exposed the handlers through the legacy request/response. However there were some mismatches (such as legacy protocol always returns Map<String, Object?> but some LSP requests return Lists, LSP using int|String IDs, and LSP having numeric error codes that don't match legacy string error codes). This change uses LSP's request and Response by wrapping them inside a standard (legacy) handler. The LSP-over-Legacy handler has become a standard handler, and the params contain an "lspMessage" field that holds an LSP message, and the result contains an "lspResponse" field that contains an LSP response. If an LSP handler returns an error, it will be returned as an error inside the LSP response, which will be in a _successful_ legacy request (since that's how we can return an LSP response - as the result). Change-Id: I67973590ab32f3543d1a6e1b7279974e5e8832bc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/315201 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> |
||
---|---|---|
.. | ||
example | ||
lib | ||
test | ||
analysis_options.yaml | ||
CHANGELOG.md | ||
LICENSE | ||
OWNERS | ||
pubspec.yaml | ||
README.md |
package:analysis_server_client
is a client wrapper over the Analysis Server.
Update: this package has been discontinued
This package has been discontinued and will not receive further updates.
People who need similar functionality could:
- continue to use the last published version; it should continue to be able to talk to the analysis server for the foreseeable future
- fork the package and maintain that fork (we don't expect that the analysis server protocol will evolve significantly)
- see if their use case could instead be satisfied by talking to the analysis
server over the LSP protocol (
dart language-server --protocol=lsp
)
We welcome feedback about this at #50262; that would also be a good place to discuss alternatives.
Overview
-
Instances of Server manage a connection to an analysis server process, and facilitate communication to and from the server.
-
The Protocol library provides constants and classes to build requests for the server and decode responses and notifications from the server.
Example
The example uses the Server to launch the analysis server, analyze all *.dart files in the specified directory, display the results, and shutdown the analysis server.
References
For more about the analysis server, see the Analysis Server page.