5b32f55a3a
Queries can technically be also accessed within component templates e.g. ```html <my-comp [binding]="myQuery"></my-comp> ``` In that case the query with the property "myQuery" is accessed statically and needs to be marked with `static: true`. There are other edge cases that need to be handled as the template property read doesn't necessarily resolve to the actual query property. For example: ```html <foo #myQuery></foo> <my-comp [binding]="myQuery"></my-comp> ``` In this scenario the binding doesn't refer to the actual query because the template reference variable takes precedence. The query doesn't need to be marked with "static: true" this time. This commit ensures that the `static-query` migration schematic now handles this cases properly. Also template property reads that access queries from within a `<ng-template>` are ignored as these can't access the query before the view has been initialized. Resolves FW-1216 PR Close #29713
26 lines
821 B
TypeScript
26 lines
821 B
TypeScript
/**
|
|
* @license
|
|
* Copyright Google Inc. All Rights Reserved.
|
|
*
|
|
* Use of this source code is governed by an MIT-style license that can be
|
|
* found in the LICENSE file at https://angular.io/license
|
|
*/
|
|
|
|
import {parseTemplate} from '@angular/compiler';
|
|
import {Node} from '@angular/compiler/src/render3/r3_ast';
|
|
|
|
/**
|
|
* Parses the given HTML content using the Angular compiler. In case the parsing
|
|
* fails, null is being returned.
|
|
*/
|
|
export function parseHtmlGracefully(htmlContent: string, filePath: string): Node[]|null {
|
|
try {
|
|
return parseTemplate(htmlContent, filePath).nodes;
|
|
} catch {
|
|
// Do nothing if the template couldn't be parsed. We don't want to throw any
|
|
// exception if a template is syntactically not valid. e.g. template could be
|
|
// using preprocessor syntax.
|
|
return null;
|
|
}
|
|
}
|