Allows wrapping up a
Builder as a
Transformer so that it can be run in
Builder instance with
new BuilderTransformer(builder) and use it
like any other Transformer. The Builder used this way must follow the rules of
other Transformers, it cannot use inputs from outside the package where the
Transformer is specified in pubspec.yaml
Transformer instance with
new TransformerBuilder(transformer) and
run as any other
Builder. The Transformer instance used this way must follow
the rules of other Builders:
Please file feature requests and bugs at the issue tracker.
srcimport from package:build.
AnalysisOptionswith the following changes:
This makes the resolver implementation identical to the experience using the bazel_codegen, but it is technically a breaking change if you relied on the current behavior.
TransformerAssetReader#findAssetsnow returns a
Stream<AssetId>to match the latest
buildpackage, but this isn't considered a breaking change since the api is unsupported and throws in this implementation.
ResourceManagerfor all calls to
BuilderTransformer. This makes
Resources be shared across all build steps for a given package and Builder.
BuilderTransformeris now an
AggregateTransformer. This should be transparent for most use cases but could have errors if an instance was assigned to a variable of type
BuilderTransformerno longer accepts a
Resolversinstance, instead it will create and manage Resolvers on its own.
TransformerBuildermust be constructed with a
buildExtensionconfiguration. Transformers wrapped as a builder must have outputs which vary only by input extension.
Updated to reflect the new support for reading/writing as bytes in the
package, and the removal of the
BuilderTransformernow supports wrapping transformers that read or write their inputs as bytes.
isLibraryto check whether an Asset is a Library and throws an exception rather than returns null on
getLibrarywhen it isn't
lib/src/util/barback.dartwhich contains internal only utilities. Specifically, the following items are no longer public (some are deleted entirely or had breaking changes as well):
complete()call in BuildStepImpl
Add this to your package's pubspec.yaml file:
dependencies: build_barback: "^0.5.0+4"
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.5.0+4||May 14, 2018|
|0.5.0+3||Feb 3, 2018|
|0.5.0+2||Jan 18, 2018|
|0.5.0+1||Jan 2, 2018|
|0.5.0||Dec 7, 2017|
|0.4.0+2||Nov 2, 2017|
|0.4.0+1||Sep 21, 2017|
|0.4.0||Aug 14, 2017|
|0.3.0||Jul 18, 2017|
|0.2.2||May 4, 2017|
We analyzed this package on Jun 12, 2018, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
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, other
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
|Dart SDK||>=2.0.0-dev.9 <2.0.0|