A batteries included package to validate whether the working revision of a Dart package conforms to testing and contribution requirements. Stated simply, "something to run on continuous integration before merging pull requests".
$ pub global activate presubmit $ pub global run presubmit \ $ --[no]dartanalyzer \ $ --[no]dartfmt \ $ --[no]tests \ $ --path <location of package, defaults to current>
A high-level list of work required to get this close to an initial release:
pub run presubmit)
pub run test)
Add this to your package's pubspec.yaml file:
dependencies: presubmit: "^0.0.2"
You can install packages from the command line:
$ pub get
$ flutter packages get
Alternatively, your editor might support
pub get or
Check the docs for your editor to learn more.
|0.0.2||Feb 25, 2017|
|0.0.1||Jan 20, 2017|
|0.0.0||Jan 20, 2017|
We analyzed this package, and provided a score, details, and suggestions below.
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]
Detected platforms: Flutter, web, other
No platform restriction found in libraries.
Changelog entries help clients to follow the progress in your code.
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 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.dartor you could also use