Paul Berry
701cd77844
The analyzer team has decided to adopt the convention of using `TODO` comments to document long term issues that should persist in the codebase, and `FIXME` comments to document short term issues that need immediate attention. They may even consider adding a presubmit hook to ensure that `FIXME` comments are only used during local development. Accordingly, it makes sense to suppress `TODO` comments from being surfaced to the IDE "problems" view (since there are hundreds of them, and they're not immediately actionable). This makes VSCode's "problems" view much more usable in "tree" mode. (See also https://dart-review.googlesource.com/c/sdk/+/295662, which made the corresponding change to the `analysis_server` and `analyzer` packages, and https://dart-review.googlesource.com/c/sdk/+/325121, which made the corresponding change to the `linter` package). Change-Id: Ifbd2f6bed468408b1906b25ab94f745eed0b3e55 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/358980 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@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.