Sam Rawlins
793aeaee01
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>
A framework for building plugins for the analysis server.
Usage
Note: The plugin support is not currently available for general use.
Plugins are written in Dart and are run in the same VM as the analysis server. The analysis server runs each plugin in a separate isolate and communicates with the plugin using a plugin API. This API is similar to the API used by the analysis server to communicate with clients.
Plugins are automatically discovered and run by the analysis server.
This package contains support code to make it easier to write a plugin. There is a tutorial describing how to use the support in this package.
Support
Post issues and feature requests on the issue tracker.
Questions and discussions are welcome at the Dart Analyzer Discussion Group.
License
See the LICENSE file.