commit | 64c222d368bab925fe855c201a6b5f49f82bb7eb | [log] [tgz] |
---|---|---|
author | stuartmorgan <stuartmorgan@google.com> | Thu Dec 09 17:02:24 2021 -0500 |
committer | GitHub <noreply@github.com> | Thu Dec 09 14:02:24 2021 -0800 |
tree | b3b6efdff7a384e285155c37a2cc939f11dfb327 | |
parent | 33968c0e9e223ca64dbd6e07dc4addf81cb7269f [diff] |
Move custom analysis options into sub-packages (#4603) When the legacy analysis options were bulk-added to the repository to allow transitioning incrementally to the Flutter analysis options, they were added to top-level plugin groups. This makes it harder to migrate incrementally, and also means that when we add a new sub-package (e.g, a web or desktop implementation) it's automatically using the legacy options. This moves all the legacy option files into each individual package, and updates the allow list for the tool accordingly, so that migration can be done package by package.
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.