Changes in polymer-expressions to prepare for codegen in polymer:

pkg/polymer_expressions/CHANGELOG.md

Index: pkg/polymer_expressions/CHANGELOG.md
diff --git a/pkg/polymer_expressions/CHANGELOG.md b/pkg/polymer_expressions/CHANGELOG.md
new file mode 100644
index 0000000000000000000000000000000000000000..8b2cb5c4592e74fd7884dbeaaec040695394e338
--- /dev/null
+++ b/pkg/polymer_expressions/CHANGELOG.md
@@ -0,0 +1,18 @@
+# changelog
+
+This file contains highlights of what changes on each version of the
+polymer_expressions package.
+
+#### Pub version 0.10.0-dev

[Siggi Cherem (dart-lang), 2014/03/21 01:43:46]

anything else to add here?
 - I used to have a comment about globals now take precedence over the model
properties, but I believe that was true before too.

+  * package:polymer_expressions no longer declares @MirrosUsed. The package uses
+    mirrors at development time, but assumes frameworks like polymer will
+    generate code that replaces the use of mirrors. If you use this directly,
+    you might need to do code generation as well, or add the @MirrorsUsed
+    declaration. This can be done either explicitly or by importing the old
+    settings from 'package:observe/mirrors_used.dart' (which include
+    @reflectable and @observable by default).
+
+  * Errors that occur within bindings are now thrown asycnhronously. We used to

[Jennifer Messerly, 2014/03/21 20:08:54]

can this same change be made to PathObserver/PropertyPath? Or is it done
already?

[Siggi Cherem (dart-lang), 2014/03/21 21:09:47]

It's not done already, but I can look into it. Is it OK to do it as a separate
change?

[Jennifer Messerly, 2014/03/22 00:37:56]

sure :)

+    trap some errors and report them in a Logger, and we would let other errors
+    halt the rendering process. Now all errors are caught, but they are reported
+    asynchornously so they are visible even when logging is not set up.