Paul Berry
c30dd253a3
All code generation logic that uses the analyzer_utilities package's `GeneratedContent` class hierarchy is modified to use `package:analyzer_testing/package_root.dart` to locate the `pkg` directory in the root of the SDK repo. This paves the way for some follow-up work in which I intend to modify the `GeneratedContent` class hierarchy so that it tracks the locations of all code generation targets relative to the `pkg` directory rather than the individual package directories. That in turn should make it easier for code generation logic to be shared between error messages belonging to `pkg/analyzer`, `pkg/front_end`, and `pkg/_fe_analyzer_shared`. Change-Id: Iee59e977e844261f46fb62ed4e222db79db45a25 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/438061 Auto-Submit: Paul Berry <paulberry@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: 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.