angular-cn/packages/upgrade
Georgios Kalpakas d1fb066d07 fix(upgrade): use correct attribute name for upgraded component's bindings (#16128)
Previously, when using a different property/attribute name for an upgraded
component's binding (e.g. `bindings: {propName: '<attrName'}`), the property and
attribute names were swapped (e.g. using `attrName` as the property name and
`propName` as the attribute name). This resulted in unexpected behavior.

This commit fixes this using the correct names for properties and attributes.

This only affects `upgrade/dynamic`. `upgrade/static` works correctly already.

Fixes #8856

PR Close #16128
2017-04-24 12:14:03 -05:00
..
src fix(upgrade): use correct attribute name for upgraded component's bindings (#16128) 2017-04-24 12:14:03 -05:00
static feat(upgrade): allow setting the angularjs lib at runtime (#15168) 2017-04-17 14:35:55 -07:00
test fix(upgrade): use correct attribute name for upgraded component's bindings (#16128) 2017-04-24 12:14:03 -05:00
index.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
package.json build: fix paths to typings files so tsickle resolves imports correctly 2017-03-16 17:34:29 -07:00
public_api.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
rollup.config.js test: add systemjs+umd integration test (#14196) 2017-03-19 12:23:07 -05:00
tsconfig-build.json fix(upgrade): Update types for TypeScript nullability support 2017-04-18 12:07:33 -07:00