Konstantin Shcheglov
3e73e2fed4
Avoid constructing file URIs and paths directly from the host platform when analyzer code is operating on an injected ResourceProvider. Those direct conversions use the process path context, which is wrong when the provider is using a Windows path context on another host platform. Route file URI conversions through ResourceProvider, FileSource, File, and PathContext APIs instead. This keeps file names, document links, analysis options includes, navigation targets, and relative paths aligned with the active provider. Update affected tests and shared test utilities to use provider-backed URIs and paths, so they exercise the same path semantics as production code. Change-Id: Iaf7751d028273a5fa72a04d8ca60e51aee700594 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/499481 Reviewed-by: Samuel Rawlins <srawlins@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com>
A framework for building plugins for the analysis server.
Warning
This package is for legacy support and is not recommended for new plugin development.
For modern plugin implementations, use the
analysis_server_pluginpackage instead.See its documentation for the latest architecture and examples.
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.