A central place for all community made Flutter packages.
The Flutter Community is a GitHub organisation used to manage community made Flutter packages.
Our goal is to ensure packages made by the Flutter community are kept alive and maintained in one place.
To go along with the packages, we have started a Medium publication as a central location for community content to be published - especially if it relates to the packages here.
https://medium.com/flutter-community
If you want your packages to be included in the Flutter Community organization, make sure you have read and completed the following steps.
In order for the Flutter Community organization to keep track of all the submitted packages and their maintainer, all repositories are required to contain a COMMUNITY_INFO.yaml
file in the root of the repository. This file contains information about the package, pub page and maintainer.
Note, without this file your package will not be listed in the packages table.
A COMMUNITY_INFO.yaml
contains the following fields:
is_package: bool
- REQUIRED: This indicates if your repository is a package or not. This should almost always betrue
.package_name: String
- Optional: The name of your package. If this field is not present, the name of the repository of your package will be used.maintainer_name: String
- STRONGLY RECOMMENDED: The name of the current maintainer of the project (usually you).maintainer_username: String
- STRONGLY RECOMMENDED: The maintainer's GitHub username.package_description: String
- STRONGLY RECOMMENDED: A description of what your package does.pub_package_name: String
- Recommended: The name of your package as listed on Dart pub.
Fill this in if the name of your package on Dart pub is different to the name of your repository or thepackage_name
in yourCOMMUNITY_INFO.yaml
.
When in doubt, leave empty.
Your COMMUNITY_INFO.yaml
file should look something like this (example taken from after_layout):
is_package: true
package_name: after_layout
maintainer_name: Simon Lightfoot
maintainer_username: slightfoot
package_description: Brings functionality to execute code after the first layout of a widget has been performed.
pub_package_name: after_layout
If you've prepared your packages, you can either:
- RECOMMENDED: Open an issue on the
community
repository. - Contact us in the Study Group.
This is only a branding change. The idea is to promote the integrity of packages. Not all packaged will be accepted.
Name | Release | Description | Maintainer |
---|---|---|---|
after_layout | Brings functionality to execute code after the first layout of a widget has been performed. | Simon Lightfoot | |
sticky_headers | Lets you place headers on scrollable content that will stick to the top of the container whilst the content is scrolled. | Simon Lightfoot | |
get_it | Simple direct Service Locator that allows to decouple the interface from a concrete implementation and to access the concrete implementation from everywhere in your App. | Thomas Burkhart | |
rx_command | Reactive event handler wrapper class inspired by ReactiveUI. | Thomas Burkhart | |
draggable_scrollbar | A scrollbar that can be dragged for quickly navigation through a vertical list with optional label next to scrollthumb with information about current item. | Marina Kuznetsova |