Brian Wilkerson
1e93347fc2
This merges the 3 concrete classes into a single class. We were not really testing Dart 1 behavior, and the extension methods experiment is enabled by default. I also renamed several of the tests to conform more closely to the convention we use. I did not alter the bodies of any of the tests, so we're testing exactly the same things after this CL as before. In future CLs, as I add more information to OpType (for the new relevance computations), I plan to subdivide the tests based on the type of the AST node being tested, which will split up the tests and allow for shorter test names. Change-Id: I717c5697817d9f96d050318f2f39da85dff23422 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/142203 Reviewed-by: Jaime Wren <jwren@google.com> Reviewed-by: Phil Quitslund <pquitslund@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
analyzer_plugin
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.