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

docs: clarify the shortcomings of local variable technique for parent-child component interactions (#42331) 

Closes #38302

PR Close #42331
This commit is contained in:
Joey Perrott 2021-05-25 14:34:28 -07:00 committed by Andrew Kushnir
parent cdb8f556fb
commit fa0144fde6
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
aio/content/guide/component-interaction.md
View File

@ -300,8 +300,11 @@ The *local variable* approach is easy. But it is limited because
the parent-child wiring must be done entirely within the parent template. the parent-child wiring must be done entirely within the parent template.
The parent component *itself* has no access to the child. The parent component *itself* has no access to the child.
You can't use the *local variable* technique if an instance of the parent component *class* You can't use the *local variable* technique if the parent component's *class* relies on the
must read or write child component values or must call child component methods. child component's *class*. The parent-child relationship of the components is not established
within each components respective *class* with the *local variable* technique. Since the *class*
instances are not connected to one another, the parent *class* cannot access the child *class*
properties and methods.
When the parent component *class* requires that kind of access, When the parent component *class* requires that kind of access,
***inject*** the child component into the parent as a *ViewChild*. ***inject*** the child component into the parent as a *ViewChild*.