Sam Rawlins
b8b1e01173
In the recent change, https://dart-review.googlesource.com/c/sdk/+/503040, the asynchronous nature of the change required adding _new_ hooks to track that the plugin isolate is analyzing or not. I missed removing the old hooks. The result is that an invocation of `dart analyze` will get a notification from the plugin isolate that it is analyzing, and then _immediately_ a notification indicating that it is not. So this change removes the old hooks. Change-Id: Idc871d25c043ee1be94030729a1fd8226bdc753f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/504140 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
analysis_server_plugin package
This package offers support for writing Dart analysis server plugins, for Dart 3.10 (Flutter 3.38) and later.
Analysis server plugins empower developers to contribute their own Dart static
analysis in IDEs and at the command line via dart analyze and flutter analyze. Analysis server plugins can offer the following static analyses:
- analysis rules, which report diagnostics in the IDE, and at the command line
- IDE quick fixes, which are local refactorings offered to users to correct a given diagnostic
- IDE quick assists, which are local refactorings that are offered at specific syntax nodes in code, but do not necessarily correct a static code issue
Review the following documents for how to write and how to use analysis server plugins: