Konstantin Shcheglov
58f3098650
There might be some false negatives, when there *is* another top-level declaration with the same name as we are removing. But this is a pre-existing conflict, so I think we should not be very concerned. At some point we might collect initial potentially conflicting names using the same SyntacticScopeNamesCollector instead of element model. With element model we don't know about parser recovery. R=brianwilkerson@google.com Bug: https://github.com/dart-lang/sdk/issues/36890 Change-Id: Ia05db299990f41f16feb493c2812237be84f3d2e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/101902 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@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.