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

fix(aio): fix incorrect image URLs in guides

This commit is contained in:
Georgios Kalpakas 2017-04-26 15:12:22 +03:00 committed by Pete Bacon Darwin
parent 6561d46349
commit 96648ba98a
2 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
aio/content/guide/dependency-injection-in-action.md
View File

@ -171,7 +171,7 @@ Once all the dependencies are in place, the `AppComponent` displays the user inf
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/logged-in-user.png" alt="Logged In User"></img> <img src="content/images/guide/dependency-injection-in-action/logged-in-user.png" alt="Logged In User"></img>
</figure> </figure>
@ -337,7 +337,7 @@ Find this example in <live-example name="dependency-injection-in-action">live co
and confirm that the three `HeroBioComponent` instances have their own cached hero data. and confirm that the three `HeroBioComponent` instances have their own cached hero data.
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/hero-bios.png" alt="Bios"></img> <img src="content/images/guide/dependency-injection-in-action/hero-bios.png" alt="Bios"></img>
</figure> </figure>
@ -403,7 +403,7 @@ placing it in the `<ng-content>` slot of the `HeroBioComponent` template:
It looks like this, with the hero's telephone number from `HeroContactComponent` projected above the hero description: It looks like this, with the hero's telephone number from `HeroContactComponent` projected above the hero description:
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/hero-bio-and-content.png" alt="bio and contact"></img> <img src="content/images/guide/dependency-injection-in-action/hero-bio-and-content.png" alt="bio and contact"></img>
</figure> </figure>
@ -440,7 +440,7 @@ Thanks to `@Optional()`, Angular sets the `loggerService` to null and the rest o
Here's the `HeroBiosAndContactsComponent` in action. Here's the `HeroBiosAndContactsComponent` in action.
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/hero-bios-and-contacts.png" alt="Bios with contact into"></img> <img src="content/images/guide/dependency-injection-in-action/hero-bios-and-contacts.png" alt="Bios with contact into"></img>
</figure> </figure>
@ -450,7 +450,7 @@ until it finds the logger at the `AppComponent` level. The logger logic kicks in
with the gratuitous "!!!", indicating that the logger was found. with the gratuitous "!!!", indicating that the logger was found.
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/hero-bio-contact-no-host.png" alt="Without @Host"></img> <img src="content/images/guide/dependency-injection-in-action/hero-bio-contact-no-host.png" alt="Without @Host"></img>
</figure> </figure>
@ -495,7 +495,7 @@ first without a value (yielding the default color) and then with an assigned col
The following image shows the effect of mousing over the `<hero-bios-and-contacts>` tag. The following image shows the effect of mousing over the `<hero-bios-and-contacts>` tag.
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/highlight.png" alt="Highlighted bios"></img> <img src="content/images/guide/dependency-injection-in-action/highlight.png" alt="Highlighted bios"></img>
</figure> </figure>
{@a providers} {@a providers}
@ -573,7 +573,7 @@ The `HeroOfTheMonthComponent` example demonstrates many of the alternatives and
It's visually simple: a few properties and the logs produced by a logger. It's visually simple: a few properties and the logs produced by a logger.
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/hero-of-month.png" alt="Hero of the month" width="300px"></img> <img src="content/images/guide/dependency-injection-in-action/hero-of-month.png" alt="Hero of the month" width="300px"></img>
</figure> </figure>
@ -728,7 +728,7 @@ Now put it to use in a simplified version of the `HeroOfTheMonthComponent`.
The `HeroOfTheMonthComponent` constructor's `logger` parameter is typed as `MinimalLogger` so only the `logs` and `logInfo` members are visible in a TypeScript-aware editor: The `HeroOfTheMonthComponent` constructor's `logger` parameter is typed as `MinimalLogger` so only the `logs` and `logInfo` members are visible in a TypeScript-aware editor:
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/minimal-logger-intellisense.png" alt="MinimalLogger restricted API"></img> <img src="content/images/guide/dependency-injection-in-action/minimal-logger-intellisense.png" alt="MinimalLogger restricted API"></img>
</figure> </figure>
@ -743,7 +743,7 @@ Behind the scenes, Angular actually sets the `logger` parameter to the full serv
The following image, which displays the logging date, confirms the point: The following image, which displays the logging date, confirms the point:
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/date-logger-entry.png" alt="DateLoggerService entry" width="300px"></img> <img src="content/images/guide/dependency-injection-in-action/date-logger-entry.png" alt="DateLoggerService entry" width="300px"></img>
</figure> </figure>
@ -941,7 +941,7 @@ to display a *sorted* list of heroes.
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/sorted-heroes.png" alt="Sorted Heroes"></img> <img src="content/images/guide/dependency-injection-in-action/sorted-heroes.png" alt="Sorted Heroes"></img>
</figure> </figure>
@ -1154,7 +1154,7 @@ the same way you've done it before:
Here's *Alex* and family in action: Here's *Alex* and family in action:
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/alex.png" alt="Alex in action"></img> <img src="content/images/guide/dependency-injection-in-action/alex.png" alt="Alex in action"></img>
</figure> </figure>
@ -1215,7 +1215,7 @@ Here's *Alice*, *Barry* and family in action:
<figure class='image-display'> <figure class='image-display'>
<img src="content/images/guide/dependency-injection/alice.png" alt="Alice in action"></img> <img src="content/images/guide/dependency-injection-in-action/alice.png" alt="Alice in action"></img>
</figure> </figure>

12
aio/content/guide/ngmodule.md
View File

@ -185,7 +185,7 @@ compiles the application in the browser and then launches the app.
The samples in this page demonstrate the dynamic bootstrapping approach. The samples in this page demonstrate the dynamic bootstrapping approach.
<live-example embedded plnkr="minimal.0" img="devguide/ngmodule/minimal-plunker.png">Try the live example.</live-example> <live-example embedded plnkr="minimal.0" img="guide/ngmodule/minimal-plunker.png">Try the live example.</live-example>
### Static bootstrapping with the ahead-of-time (AOT) compiler ### Static bootstrapping with the ahead-of-time (AOT) compiler
@ -682,7 +682,7 @@ The app file structure looks like this:
Try the example: Try the example:
<live-example embedded plnkr="contact.1b" img="devguide/ngmodule/contact-1b-plunker.png"></live-example> <live-example embedded plnkr="contact.1b" img="guide/ngmodule/contact-1b-plunker.png"></live-example>
{@a resolve-conflicts} {@a resolve-conflicts}
@ -896,7 +896,7 @@ There's a lot to like in the revised `AppModule`.
Try this `ContactModule` version of the sample. Try this `ContactModule` version of the sample.
<live-example embedded plnkr="contact.2" img="devguide/ngmodule/contact-2-plunker.png">Try the live example.</live-example> <live-example embedded plnkr="contact.2" img="guide/ngmodule/contact-2-plunker.png">Try the live example.</live-example>
{@a lazy-load} {@a lazy-load}
@ -915,7 +915,7 @@ Their specifics aren't important to the story and this page doesn't discuss ever
Examine and download the complete source for this version from Examine and download the complete source for this version from
the <live-example plnkr="pre-shared.3" img="devguide/ngmodule/v3-plunker.png">live example.</live-example> the <live-example plnkr="pre-shared.3" img="guide/ngmodule/v3-plunker.png">live example.</live-example>
</div> </div>
@ -1194,7 +1194,7 @@ It imports the `HeroRoutingModule` from `hero-routing.module.ts` just as `Contac
The `CrisisModule` is much the same. The `CrisisModule` is much the same.
<live-example embedded plnkr="pre-shared.3" img="devguide/ngmodule/v3-plunker.png">Try the live example.</live-example> <live-example embedded plnkr="pre-shared.3" img="guide/ngmodule/v3-plunker.png">Try the live example.</live-example>
{@a shared-module} {@a shared-module}
@ -1549,7 +1549,7 @@ Now `parentModule` exists and the constructor throws the error.
### Conclusion ### Conclusion
You made it! You can examine and download the complete source for this final version from the live example. You made it! You can examine and download the complete source for this final version from the live example.
<live-example embedded img="devguide/ngmodule/final-plunker.png"></live-example> <live-example embedded img="guide/ngmodule/final-plunker.png"></live-example>
### Frequently asked questions ### Frequently asked questions