Andrew Kushnir 5a2c3ff8b5 fix(ivy): proper component resolution in case of inheritance (#28439) ... Ivy allows Components to extend Directives (but not the other way around) and as a result we may have Component and Directive annotations present at the same time. The logic that resolves annotations to pick the necessary one didn't take this into account and as a result Components were recognized as Directives (and vice versa) in case of inheritance. This change updates the resolution logic by picking known annotation that is the nearest one (in inheritance tree) and compares it with expected type. That should help avoid mis-classification of Components/Directives during resolution. PR Close #28439		2019-02-05 23:29:04 -05:00
..
src	fix(ivy): proper component resolution in case of inheritance (#28439)	2019-02-05 23:29:04 -05:00
BUILD.bazel	build: set a default module_name for ts_library rules (#28051)	2019-01-18 10:16:39 -08:00
index.ts	build: publish tree of files rather than FESMs (#18541)	2017-08-31 15:34:50 -07:00
package.json	fix: correct several esm2015 entry-points in package.jsons (#22892)	2018-03-20 13:30:08 -07:00
public_api.ts	build: refactor ambient node & jasmine types so they are only included where needed (#25491)	2018-08-16 13:46:43 -07:00
rollup.config.js	feat(ivy): implement TestBed (#25369)	2018-08-14 11:58:47 -07:00
tsconfig-build.json	feat(ivy): implement TestBed (#25369)	2018-08-14 11:58:47 -07:00