One can see that we have bare HTML in these signature-in-comments, like: "contextMessages": optional List<DiagnosticMessage> These are flagged by the unintended_html_in_doc_comment lint rule. This CL solves this by indenting these signatures 4 spaces, making them Markdown indented code blocks. Alternatively we could use backticks. Backticks would make the comments taller; indenting makes them wider. I would prioritize whichever style is less intrusive when reading them in plain text, which I think would be to use indentation. Change-Id: I019d9073e994a505325194ceeac3c6e0635d947e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/453642 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
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.