fix: same examples

This commit is contained in:
Zhicheng Wang 2017-08-04 08:58:13 +08:00
parent 19088b76f8
commit cc33798597
2 changed files with 2 additions and 7 deletions

View File

@ -584,7 +584,7 @@ Add a second **input** property to `HighlightDirective` called `defaultColor`:
把第二个名叫`defaultColor`的**输入**属性添加到`HighlightDirective`中: 把第二个名叫`defaultColor`的**输入**属性添加到`HighlightDirective`中:
<code-example path="attribute-directives/src/app/highlight.directive.ts(defaultColor)" linenums="false" title="src/app/highlight.directive.ts (defaultColor)(excerpt)"> <code-example path="attribute-directives/src/app/highlight.directive.ts" linenums="false" title="src/app/highlight.directive.ts (defaultColor)(excerpt)">
</code-example> </code-example>

View File

@ -615,7 +615,7 @@ Use `ngOnInit()` for two main reasons:
Experienced developers agree that components should be cheap and safe to construct. Experienced developers agree that components should be cheap and safe to construct.
有经验的开发者认同组件的构建应该很便宜和安全。 有经验的开发者认同组件的构建应该很便宜和安全。
<div class="l-sub-section"> <div class="l-sub-section">
@ -1012,11 +1012,6 @@ which can only be reached by querying for them via the property decorated with
下列*AfterContent*钩子基于*子级内容*中值的变化而采取相应的行动,这里我们只能通过带有[@ContentChild](api/core/ContentChild)装饰器的属性来查询到“子级内容”。 下列*AfterContent*钩子基于*子级内容*中值的变化而采取相应的行动,这里我们只能通过带有[@ContentChild](api/core/ContentChild)装饰器的属性来查询到“子级内容”。
<code-example path="lifecycle-hooks/src/app/after.component.ts" region="hooks" title="AfterContentComponent (class excerpts)" linenums="false">
</code-example>
{@a no-unidirectional-flow-worries} {@a no-unidirectional-flow-worries}
### No unidirectional flow worries with _AfterContent_ ### No unidirectional flow worries with _AfterContent_