George Kalpakas 1465372a0e fix(elements): do not break when the constructor of an Angular Element is not called (#36114) (#37226) ...

Previously, the correct behavior of Angular custom elements relied on
the constructor being called (and thus the `injector` property being
initialized). However, some polyfills (e.g. `document-register-element`)
do not call the constructor of custom elements, which resulted in the
`injector` property being undefined and the `NgElementStrategy` failing
to be instantiated.

This commit fixes it by being tolerant to the `injector` property being
undefined and falling back to the injector passed to the
`createCustomElement()` config.

NOTE:
We don't have proper tests exercising the situation where the
constructor is not called. For now this is tested using a Google
internal test suite (which is how this issue was caught).
This commit also adds a rudimentary unit test to emulate this situation.

PR Close #36114

PR Close #37226

2020-05-20 14:49:21 -07:00

..

schematics

build: reformat repo to new clang@1.4.0 (#36628)

2020-04-14 12:07:43 -07:00

src

fix(elements): do not break when the constructor of an Angular Element is not called (#36114) (#37226)

2020-05-20 14:49:21 -07:00

test

fix(elements): do not break when the constructor of an Angular Element is not called (#36114) (#37226)

2020-05-20 14:49:21 -07:00

BUILD.bazel

build: provide full paths to ts_api_guardian_test_npm_package and ts_api_guardian_test (#36034)

2020-03-12 09:49:00 -07:00

index.ts

feat(elements): add support for creating custom elements (#22413)

2018-03-16 12:39:07 -07:00

package.json

build(packaging): add repository.directory field to package.jsons (#27544)

2020-02-25 13:12:45 -08:00

PACKAGE.md

docs: add package doc files (#26047)

2018-10-05 15:42:14 -07:00

public_api.ts

build: reformat repo to new clang@1.4.0 (#36628)

2020-04-14 12:07:43 -07:00