George Kalpakas 9ba46d9f88 fix(elements): correctly handle setting inputs to `undefined` (#36140) ... Previously, when an input property was initially set to `undefined` it would not be correctly recognized as a change (and trigger `ngOnChanges()`). This commit ensures that explicitly setting an input to `undefined` is correctly handled the same as setting the property to any other value. This aligns the behavior of Angular custom elements with that of the corresponding components when used directly (not as custom elements). PR Close #36140		2020-03-24 10:29:33 -07:00
..
component-factory-strategy.ts	fix(elements): correctly handle setting inputs to `undefined` (#36140)	2020-03-24 10:29:33 -07:00
create-custom-element.ts	build: typescript 3.8 support (#35864)	2020-03-10 17:51:20 -04:00
element-strategy.ts	docs: convert all `@experimental` tags to `@publicApi` tags (#26595)	2018-10-19 14:35:52 -07:00
extract-projectable-nodes.ts	feat(elements): add support for creating custom elements (#22413)	2018-03-16 12:39:07 -07:00
utils.ts	refactor: remove toplevel property accesses (#29329)	2019-05-16 12:08:49 -07:00
version.ts	docs: convert all `@experimental` tags to `@publicApi` tags (#26595)	2018-10-19 14:35:52 -07:00