Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(21)

Unified Diff: pkg/barback/CHANGELOG.md

Issue 199133003: Add a changelog to barback. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Created 6 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: pkg/barback/CHANGELOG.md
diff --git a/pkg/barback/CHANGELOG.md b/pkg/barback/CHANGELOG.md
new file mode 100644
index 0000000000000000000000000000000000000000..c355a355596c51d656542ca3bd9601740f663de0
--- /dev/null
+++ b/pkg/barback/CHANGELOG.md
@@ -0,0 +1,24 @@
+## 0.12.0
+
+* Add a `Transform.logger.fine` function that doesn't print its messages by
+ default. When using Barback with pub in verbose mode, these messages will be
+ printed.
+
+* `Transformer.allowedExtensions` now supports extensions containing multiple
+ periods, such as `.dart.js`.
+
+* Transforms now pass their primary inputs through to the next phase by default.
Bob Nystrom 2014/03/14 00:01:55 "Transforms" -> "Transformers"
nweiz 2014/03/14 00:06:52 I thought we used "transformer" to refer to the cl
Bob Nystrom 2014/03/14 00:24:17 SGTM.
+ A transformer may still overwrite its primary input without causing a
+ collision. If a transformer doesn't overwrite its primary input, it may cause
+ it not to be passed through by calling `Transform.consumePrimary`. The primary
+ input will be consumed by default if a transformer throws an error.
+
+* If an input requested with `Transform.getInput`, `Transform.readInput`, or
+ `Transform.readInputAsString` cannot be found, an `AssetNotFoundException`
+ will be thrown. This was always what the documentation said, but previously a
+ `MissingInputException` was thrown instead.
+
+* If a transformer calls `Transform.logger.error`, the transformer will now be
+ considered to have failed after it finishes running `apply()`. This means that
+ its outputs will not be consumed by future transformers and its primary input
+ will not be passed through to the next phase.
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698