This file contains highlights of what changes on each version of the polymer package. We will also note important changes to the polyfill packages (observe, web_components, and template_binding) if they impact polymer.
Added the ability to override the stylesheet inlining behavior. There is now an option exposed in the pubspec.yaml called inline_stylesheets
. There are two possible values, a boolean or a map. If only a boolean is supplied then that will set the global default behavior. If a map is supplied, then the keys should be file paths, and the value is a boolean. You can use the special key ‘default’ to set the default value.
For example, the following would change the default to not inline any styles, except for the foo.css file in your web folder and the bar.css file under the foo packages lib directory:
inline_stylesheets: default: false web/foo.css: true packages/foo/bar.css: true
Added inject_build_logs_in_output
option to pubspec for polymer transformers. When set to true
, this will inject a small element into your entry point pages that will display all log messages from the polymer transformers during the build step. This element is only injected when not running in release mode (ie: pub serve
but not pub build
).
unittest
._src
and similar attributes in polymer transformers.getLocationMessage
.source_maps
' Span
class to source_span
's SourceSpan
class.<head>
.<polymer-element>
.@
are no longer supported.@published
by default is no longer reflected as an attribute by default. This might break if you try to use the attribute in places like CSS selectors. To make it reflected back to an attribute use @PublishedProperty(reflect: true)
.<link rel="import" href="packages/polymer/polymer.html">
@ObserveProperty('foo bar.baz') myMethod() {...}
will cause myMethod to be called when “foo” or “bar.baz” changes.