package:buildto allow version
BuilderFactoryin favor of the typedef from
package:build. The factories now take a
BuilderOptionsargument rather than
noArgshave been dropped. These are unused from the template file in
rules_dartwhich is the supported approach.
Add this to your package's pubspec.yaml file:
dependencies: _bazel_codegen: ^0.3.2
You can install packages from the command line:
$ pub get
$ flutter packages get
Alternatively, your editor might support
pub get or
flutter packages get.
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|0.3.2||Jul 22, 2018|
|0.3.1+2||Apr 17, 2018|
|0.3.1+1||Jan 31, 2018|
|0.3.1||Dec 11, 2017|
|0.3.0||Nov 29, 2017|
|0.2.1||Nov 3, 2017|
|0.1.7||Aug 14, 2017|
|0.1.6||Apr 26, 2017|
|0.1.5||Apr 25, 2017|
|0.1.4||Apr 17, 2017|
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Aug 10, 2018, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: Flutter, other
Readme should inform others about your project, what it does, and how they can use it.
The description is too short.
Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.
Package is pre-v1 release.
While there is nothing inherently wrong with versions of
0.*.*, it usually means that the author is still experimenting with the general direction of the API.
Maintain an example.
Create a short demo in the
example/ directory to show how to use this package. Common file name patterns include:
example.dart or you could also use
|Dart SDK||>=2.0.0-dev.32 <3.0.0|