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

docs: Typo fixes in hierarchical DI guide (#32536) 

Introduce minor typo fixes in the guide for hierarchical dependency injection

PR Close #32536
This commit is contained in:
Aristeidis Bampakos 2019-09-07 18:48:40 +03:00 committed by Andrew Kushnir
parent a0d04c628c
commit cd4021ba41
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
aio/content/guide/hierarchical-dependency-injection.md
View File

@ -3,7 +3,7 @@
Injectors in Angular have rules that you can leverage to Injectors in Angular have rules that you can leverage to
achieve the desired visibility of injectables in your apps. achieve the desired visibility of injectables in your apps.
By understanding these rules, you can determine in which By understanding these rules, you can determine in which
NgModule or component you should declare a provider. NgModule, Component or Directive you should declare a provider.
## Two injector hierarchies ## Two injector hierarchies
@ -592,7 +592,7 @@ its search at the `<#VIEW>` belonging to `<app-child>` (`<#VIEW>` is
included because it is injected from `@Component()`) and ends with included because it is injected from `@Component()`) and ends with
`<app-child>`. In this case, the `FlowerService` is resolved in the `<app-child>`. In this case, the `FlowerService` is resolved in the
`<app-child>`'s `providers` array with sunflower 🌻. The injector doesn't `<app-child>`'s `providers` array with sunflower 🌻. The injector doesn't
have to look any further in the injector tree. It stops as soon as it as it have to look any further in the injector tree. It stops as soon as it
finds the `FlowerService` and never sees the 🌺 (red hibiscus). finds the `FlowerService` and never sees the 🌺 (red hibiscus).
@ -618,7 +618,7 @@ set it up on your own, skip ahead to [Modifying service availability](guide/hier
The example app features a second service, the `AnimalService` to The example app features a second service, the `AnimalService` to
demonstrate `viewProviders`. demonstrate `viewProviders`.
First, create an `AnimalService` with an `emoji` property of whale 🐳: First, create an `AnimalService` with an `emoji` property of 🐳 (whale):
<code-example path="providers-viewproviders/src/app/animal.service.ts" header="providers-viewproviders/src/app/animal.service.ts" region="animal-service"> <code-example path="providers-viewproviders/src/app/animal.service.ts" header="providers-viewproviders/src/app/animal.service.ts" region="animal-service">
@ -795,7 +795,7 @@ The `AnimalService` in the logical tree would look like this:
</app-root> </app-root>
``` ```
The projected content of `<app-inspector>` sees the whale 🐳, not The projected content of `<app-inspector>` sees the 🐳 (whale), not
the 🐶 (puppy), because the the 🐶 (puppy), because the
🐶 (puppy) is inside the `<app-child>` `<#VIEW>`. The `<app-inspector>` can 🐶 (puppy) is inside the `<app-child>` `<#VIEW>`. The `<app-inspector>` can
only see the 🐶 (puppy) only see the 🐶 (puppy)