Skip to content
This repository was archived by the owner on Dec 4, 2017. It is now read-only.

Commit 66984d5

Browse files
committed
Revert "Template Expression Operators Copy Edit "
This reverts commit d081171.
1 parent 14bd476 commit 66984d5

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

public/docs/ts/latest/guide/template-syntax.jade

+9-9
Original file line numberDiff line numberDiff line change
@@ -1401,27 +1401,27 @@ h3#aliasing-io Aliasing input/output properties
14011401
:marked
14021402
<a id="pipe"></a>
14031403
### The pipe operator ( | )
1404-
Pipes are simple functions that accept an input value and return a transformed value.
14051404
The result of an expression might require some transformation before we’re ready to use it in a binding. For example, we might want to display a number as a currency, force text to uppercase, or filter a list and sort it.
14061405

1407-
Angular [pipes](./pipes.html) are a good choice for small transformations such as those listed above.
1408-
Pipe operators are easy to apply within template expressions, using the **pipe operator (`|`)**:
1406+
Angular [pipes](./pipes.html) are a good choice for small transformations such as these.
1407+
Pipes are simple functions that accept an input value and return a transformed value.
1408+
They're easy to apply within template expressions, using the **pipe operator (`|`)**:
14091409
+makeExample('template-syntax/ts/app/app.component.html', 'pipes-1')(format=".")
14101410
:marked
14111411
The pipe operator passes the result of an expression on the left to a pipe function on the right.
14121412

14131413
We can chain expressions through multiple pipes:
14141414
+makeExample('template-syntax/ts/app/app.component.html', 'pipes-2')(format=".")
14151415
:marked
1416-
We can also [apply parameters](./pipes.html#parameterizing-a-pipe) to a pipe:
1416+
And we can also [apply parameters](./pipes.html#parameterizing-a-pipe) to a pipe:
14171417
+makeExample('template-syntax/ts/app/app.component.html', 'pipes-3')(format=".")
14181418

14191419
block json-pipe
14201420
:marked
14211421
The `json` pipe is particularly helpful for debugging our bindings:
14221422
+makeExample('template-syntax/ts/app/app.component.html', 'pipes-json')(format=".")
14231423
:marked
1424-
The generated output would look something like this:
1424+
The generated output would look something like this
14251425
code-example(language="json").
14261426
{ "firstName": "Hercules", "lastName": "Son of Zeus",
14271427
"birthdate": "1970-02-25T08:00:00.000Z",
@@ -1433,7 +1433,7 @@ block json-pipe
14331433
### The safe navigation operator ( ?. ) and null property paths
14341434

14351435
The Angular **safe navigation operator (`?.`)** is a fluent and convenient way to guard against null and undefined values in property paths.
1436-
Here it is used to protect against against a view render failure if the `currentHero` is null:
1436+
Here it is, protecting against a view render failure if the `currentHero` is null.
14371437
+makeExample('template-syntax/ts/app/app.component.html', 'safe-2')(format=".")
14381438

14391439
block dart-safe-nav-op
@@ -1446,10 +1446,10 @@ block dart-safe-nav-op
14461446
+makeExample('template-syntax/ts/app/app.component.html', 'safe-1')(format=".")
14471447
:marked
14481448
The view still renders but the displayed value is blank; we see only "The title is" with nothing after it.
1449-
That is reasonable a behavior. At least the app doesn't crash.
1449+
That is reasonable behavior. At least the app doesn't crash.
14501450

1451-
Suppose the template expression involves a property path, as seen in this next example
1452-
where we’re displaying the `firstName` of a null hero:
1451+
Suppose the template expression involves a property path, as in this next example
1452+
where we’re displaying the `firstName` of a null hero.
14531453

14541454
code-example(language="html").
14551455
The null hero's name is {{nullHero.firstName}}

0 commit comments

Comments
 (0)