commit | 388f91630684ff19785a4c0e4a86fc01cd43c4e2 | [log] [tgz] |
---|---|---|
author | stuartmorgan <stuartmorgan@google.com> | Fri May 21 08:33:58 2021 -0700 |
committer | GitHub <noreply@github.com> | Fri May 21 08:33:58 2021 -0700 |
tree | ad0309b81e90e57d79c47fea79ac964919a671f2 | |
parent | 5c778ea0f5f6ecf54229280bab44fd1a41523c9d [diff] |
Mass pubspec.yaml cleanup (#3927) Regularizes the pubspec.yaml files of the plugins: - Changes from `homepage` to `repository` to improve the linking on pub.dev. - Adds an `issue_tracker` link that links directly to a search on that plugin's label, to improve the linking on pub.dev. - Standardizes the section order as `environment`, `flutter`, `dependencies`, `dev_dependencies`. This matches the current template, except that `flutter` is higher as it's critical information in a plugin (which should potentially be revisited in the template). - Sorts dependencies within each section. - Updates the Flutter SDK versions to 2.0.0; in practice this is already the case due to the Dart SDK version requirement, so this just makes it less confusing. - Standardizes the location of `version` in the initial block. Changes that were considered out of scope: - Actually cleaning up dependencies (e.g., removing meta where it's no longer needed). The goal was to make this PR as mechanical as possible, and to not change any actual behavior). - The example/ pubspecs (just to limit the scope of the PR; we should eventually clean those up too). - Plugins that have Plus Plugin equivalents, per repo policy, as this is a non-critical change. This does not update versions; these changes can be picked up the next time the plugins happen to be published. This also doesn't add automated enforcement. We should consider that in the future though; filed as https://github.com/flutter/flutter/issues/82913
This repo is a companion repo to the main flutter repo. It contains the source code for Flutter first-party plugins (i.e., plugins developed by the core Flutter team). Check the packages
directory for all plugins.
Flutter plugins enable access to platform-specific APIs. For more information about plugins, and how to use them, see https://flutter.dev/platform-plugins/.
These plugins are also available on pub.
Please file any issues, bugs, or feature requests in the main flutter repo.
Issues pertaining to this repository are labeled “plugin”.
If you wish to contribute a new plugin to the Flutter ecosystem, please see the documentation for developing packages and platform channels. You can store your plugin source code in any GitHub repository (the present repo is only intended for plugins developed by the core Flutter team). Once your plugin is ready you can publish to the pub repository.
If you wish to contribute a change to any of the existing plugins in this repo, please review our contribution guide, and send a pull request.
These are the available plugins in this repository.