@@ -17,7 +17,7 @@ block includes
1717 In fact, we'd like to apply them in our HTML templates as we do styles.
1818p.
1919 Welcome, Angular pipes, the simple display-value transformations that we can declare in our HTML!
20- Try the #[ + liveExampleLink2('live example' , 'pipes' )] .
20+ Try the #[ + liveExampleLink2()] .
2121
2222.l-main-section
2323:marked
@@ -169,7 +169,7 @@ figure.image-display
169169 Custom pipes must be registered manually.
170170
171171p.
172- If we try the #[ + liveExampleLink('live code' , 'pipes' ) ] example ,
172+ If we try the #[ + liveExampleLink() ] ,
173173 we can probe its behavior by changing the value and the optional exponent in the template.
174174
175175:marked
@@ -219,10 +219,10 @@ a#change-detection
219219 Here's the `FlyingHeroesPipe` implementation which follows the pattern for custom pipes we saw earlier.
220220+ makeExample('pipes/ts/app/flying-heroes.pipe.ts' , 'pure' , 'app/flying-heroes.pipe.ts' )( format ='.' )
221221
222- : marked
223- When we run the sample now we see odd behavior (try it in the [live example](/resources/live-examples/pipes/ts/plnkr.html) ).
222+ p.
223+ When we run the sample now we see odd behavior (try it in the #[ + liveExampleLink() ] ).
224224 Every hero we add is a flying hero but none of them are displayed.
225-
225+ : marked
226226 Although we're not getting the behavior we want, Angular isn't broken.
227227 It's just using a different change detection algorithm — one that ignores changes to the list or any of its items.
228228
@@ -238,7 +238,7 @@ a#change-detection
238238
239239 *If we **mutate** the #{_array}, no pipe is invoked and no display updated;
240240 if we **replace** the #{_array}, then the pipe executes and the display is updated*.
241- The *Flying Heroes* in the [live example](/resources/live-examples/pipes/ts/plnkr.html) extends the
241+ The *Flying Heroes* extends the
242242 code with checkbox switches and additional displays to help us experience these effects.
243243
244244figure.image-display
@@ -328,15 +328,15 @@ block pure-change
328328
329329 We can derive a `FlyingHeroesImpureComponent` that we derive from the `FlyingHeroesComponent`.
330330+ makeExample('pipes/ts/app/flying-heroes.component.ts' ,'impure-component' ,'app/flying-heroes.component.ts (FlyingHeroesImpureComponent)' )( format ='.' )
331- : marked
331+ p.
332332 The only substantive change is the pipe.
333- We can confirm in the [live example](/resources/live-examples/pipes/ts/plnkr.html)
334- that the *flying heroes* display updates as we enter new heroes even when we mutate the `heroes` #{_array}.
333+ We can confirm in the #[ + liveExampleLink()] that the #[ i flying heroes]
334+ display updates as we enter new heroes even when we mutate the
335+ #[ code heroes] #{_array} .
336+
335337- var _dollar = _docsFor === ' ts' ? ' $' : ' ' ;
338+ h3#async-pipe The impure #[ i AsyncPipe]
336339:marked
337- <a id="async-pipe"></a>
338- ### The impure *AsyncPipe*
339-
340340 The Angular `AsyncPipe` is an interesting example of an impure pipe.
341341 The `AsyncPipe` accepts a `#{_Promise}` or `#{_Observable}` as input
342342 and subscribes to the input automatically, eventually returning the emitted value(s).
0 commit comments