honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: correct typos in doc for template type guards (#37090) 

correct some small typos in new feature recommendation in stuctural-directives.md and reference from aot-compiler.md

PR Close #37090
This commit is contained in:
Judy Bogart 2019-12-23 13:06:42 -08:00 committed by Misko Hevery
parent 0520ecb7d0
commit 2cacab92e6
2 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
aio/content/guide/aot-compiler.md
View File

@ -621,7 +621,6 @@ Using `*ngIf` allows the TypeScript compiler to infer that the `person` used in
For more information about input type narrowing, see [Input setter coercion](guide/template-typecheck#input-setter-coercion) and [Improving template type checking for custom directives](guide/structural-directives#directive-type-checks).
### Non-null type assertion operator
Use the [non-null type assertion operator](guide/template-syntax#non-null-assertion-operator) to suppress the `Object is possibly 'undefined'` error when it is inconvenient to use `*ngIf` or when some constraint in the component ensures that the expression is always non-null when the binding expression is interpolated.

4
aio/content/guide/structural-directives.md
View File

@ -846,7 +846,7 @@ Use the type-guard properties to inform the template type checker of an expected
This section provides example of both kinds of type-guard property.
<div class="alert is-helpful>
<div class="alert is-helpful">
For more information, see [Template type checking guide](guide/template-typecheck "Template type-checking guide").
@ -962,7 +962,7 @@ Here is the source from the `src/app/` folder.
You learned
You learned:
* that structural directives manipulate HTML layout.
* to use [`<ng-container>`](guide/structural-directives#ngcontainer) as a grouping element when there is no suitable host element.