49a3fb4f96
With the parser code in the same library as the DOM classes, the `pkg/analyzer/tool/messages/generate.dart` program, which generates all of the diagnostic classes and diagnostics, _depends_ on a library with a `parse` method which depends on these diagnostic classes (in order to report errors while parsing HTML). This means that if there is any existing error (like an unknown identifier) in the existing error codes, it is impossible to generate the error codes. Since we don't need the `parse` method to generate diagnostics, we split up the library and remove the indirect dependency. Separating the parser code out removes the loop. Change-Id: Ifb9e9fd979e341ae64a1ed49aaf3758d3dcf1dee Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/287220 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com> |
||
---|---|---|
.. | ||
doc | ||
lib | ||
test | ||
tool/spec | ||
.gitignore | ||
analysis_options.yaml | ||
CHANGELOG.md | ||
LICENSE | ||
OWNERS | ||
pubspec.yaml | ||
README.md |
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.