fix(ivy): pass schemas
field to nested views (#31913)
Prior to this commit, the `schemas` configuration was applied to top-level view only. That leads to problems when using unknown props with elements inside nested views (for example generated as a result of *ngIf). This commit passes `schemas` information down to nested views to make sure that all the checks are consistent. PR Close #31913
This commit is contained in:

committed by
Alex Rickabaugh

parent
e8b8f6d09b
commit
d0d875a3fe
@ -76,7 +76,8 @@ export function ɵɵtemplate(
|
||||
resolveDirectives(tView, lView, tContainerNode, localRefs || null);
|
||||
|
||||
const embeddedTView = tContainerNode.tViews = createTView(
|
||||
-1, templateFn, consts, vars, tView.directiveRegistry, tView.pipeRegistry, null, null);
|
||||
-1, templateFn, consts, vars, tView.directiveRegistry, tView.pipeRegistry, null,
|
||||
tView.schemas);
|
||||
if (tView.queries !== null) {
|
||||
tView.queries.template(tView, tContainerNode);
|
||||
embeddedTView.queries = tView.queries.embeddedTView(tContainerNode);
|
||||
|
Reference in New Issue
Block a user