3.1.0
3.1.0
New features
-
Exposed
TouchFunctionandChangeFunctiontypedefs to make the transition
to strong-mode easier for teams relying on these function definitions. We
might remove them in a future release when they are no longer needed. -
Added a flag to use an experimental new compiler that uses the Dart analyzer
to gather metadata information. This flag will be turned on by default in
4.0:
transformers:
angular2/transform/codegen:
use_analyzer: trueWARNING: Using use_analyzer: true requires discontinuing use of the
platform_* options, and fails-fast if both flags are used. See
https://goo.gl/68VhMa for details.
WARNING: Using use_analyser: true doesn't yet work with most third-party
packages due to a bug.
Deprecations
- Using
dart:mirrors(i.e. running AngularDart without code generation) is
now formally deprecated. In4.0+code generation will be the only way to
run an AngularDart application, even in development mode. Please ensure you
are using our transformer: https://goo.gl/rRHqO7.
Bug fixes
-
CSS errors are now just warnings, and can be ignored. This is due to using
a CSS parser for encapsulation - and the AngularDart transformer aggressively
runs on all CSS files in a given package. We hope to make this smoother in a
future release. -
Do not generate
throwOnChangeschecks outside of dev-mode.
Performance
- Bypasses the deprecated event plugin system for all native DOM events.
- At runtime
interpolateis now represented by multiple functions (faster). KeyValueDiffer(NgClass,NgStyle) optimized for initial add/removals.- No longer generates event handler registrations for directive outputs.