crisbeto bf641e1b4b fix(core): incorrectly validating properties on ng-content and ng-container (#37773) ... Fixes the following issues related to how we validate properties during JIT: - The invalid property warning was printing `null` as the node name for `ng-content`. The problem is that when generating a template from `ng-content` we weren't capturing the node name. - We weren't running property validation on `ng-container` at all. This used to be supported on ViewEngine and seems like an oversight. In the process of making these changes, I found and cleaned up a few places where we were passing in `LView` unnecessarily. PR Close #37773		2020-07-15 12:39:39 -07:00
..
integrationtest	fix(bazel): ng_module rule does not expose flat module information in Ivy (#36971)	2020-07-09 22:11:17 +00:00
ngcc	fix(ngcc): report a warning if ngcc tries to use a solution-style tsconfig (#38003)	2020-07-14 13:21:31 -07:00
src	fix(ngcc): report a warning if ngcc tries to use a solution-style tsconfig (#38003)	2020-07-14 13:21:31 -07:00
test	fix(core): incorrectly validating properties on ng-content and ng-container (#37773)	2020-07-15 12:39:39 -07:00
BUILD.bazel	build(compiler-cli): fix bazel deps rules for ngtsc testing packages (#37977)	2020-07-08 12:05:22 -07:00
index.ts	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00
package.json	Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495)	2020-06-10 08:21:45 -07:00
tsconfig-build.json	build: reference zone.js from source directly instead of npm. (#33046)	2019-11-06 00:48:34 +00:00
tsconfig.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00