Konstantin Shcheglov
fd2a3cdc3a
We use previously added `CompilationUnitElementImpl.macroGeneratedContent` to access the current combined content. In order to make this work with current IntelliJ plugin, without adding new protocols, we store the generated code into a new file, and locations for macro-generated elements are in this file. Locations for elements that are not macro-generated are still in the source file. We use `ElementLocationProvider` to separate writing to the file system, and do this only in DAS. Change-Id: Ib156c67b0bf1f3474eb06584e76aa532abd597d1 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/210300 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.