Even if we assign to something that wants a different type, we might chain some property access on it later on, so it is not nice to don't suggest anything at all. Instead, we should give higher relevance to compatible types, but keep all the rest with default relevance, as we did already for everything other than instance creations. R=brianwilkerson@google.com Bug: https://github.com/flutter/flutter-intellij/issues/1107 Change-Id: I86c3c5dded4ad4cbbf28a60c0ae2847f07a3373b Reviewed-on: https://dart-review.googlesource.com/52863 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.