Fixed some typos
1.它/她 => 他/她 or other better expression. 2.some of 英雄.+它们 => 英雄.+他们 3.some of 它们.+他们 => 他们.+英雄
This commit is contained in:
parent
7146fd7edd
commit
11ef4f9cd4
@ -288,7 +288,7 @@ that it acquires from a service.
|
||||
`HeroListComponent` also has a `selectHero()` method that sets a `selectedHero` property when the user clicks to choose a hero from that list.
|
||||
|
||||
例如,`HeroListComponent`有一个`heroes`属性,它返回一个英雄数组,这个数组从一个服务获得。
|
||||
`HeroListComponent`还有一个`selectHero()`方法,当用户从列表中点选一个英雄时,就把它/她设置到`selectedHero`属性。
|
||||
`HeroListComponent`还有一个当用户从列表中点选一个英雄时设置`selectedHero`属性的`selectHero()`方法。
|
||||
|
||||
<code-example path="architecture/src/app/hero-list.component.ts" linenums="false" title="src/app/hero-list.component.ts (class)" region="class">
|
||||
|
||||
|
@ -1202,7 +1202,7 @@ takes `2` of them to be the runners-up, and returns their concatenated names.
|
||||
Look at the <live-example name="dependency-injection-in-action"></live-example>
|
||||
for the full source code.
|
||||
|
||||
该函数从`HeroService`获取英雄参赛者,从中取`2`个作为亚军,并把它们的名字拼接起来。请到<live-example name="dependency-injection-in-action"></live-example>查看全部原代码。
|
||||
该函数从`HeroService`获取英雄参赛者,从中取`2`个作为亚军,并把他们的名字拼接起来。请到<live-example name="dependency-injection-in-action"></live-example>查看全部原代码。
|
||||
|
||||
|
||||
</div>
|
||||
@ -1410,7 +1410,7 @@ The `HeroesBaseComponent` could stand on its own.
|
||||
It demands its own instance of the `HeroService` to get heroes
|
||||
and displays them in the order they arrive from the database.
|
||||
|
||||
`HeroesBaseComponent`能自己独立运行。它在自己的实例里要求`HeroService`,用来得到英雄,并将它们按照数据库返回的顺序显示出来。
|
||||
`HeroesBaseComponent`能自己独立运行。它在自己的实例里要求`HeroService`,用来得到英雄,并将他们按照数据库返回的顺序显示出来。
|
||||
|
||||
|
||||
<code-example path="dependency-injection-in-action/src/app/sorted-heroes.component.ts" region="heroes-base" title="src/app/sorted-heroes.component.ts (HeroesBaseComponent)">
|
||||
|
@ -106,7 +106,7 @@ The *Hero Employment Agency* uses this form to maintain personal information abo
|
||||
Every hero needs a job. It's the company mission to match the right hero with the right crisis.
|
||||
|
||||
这里是*英雄职业介绍所*,使用这个表单来维护候选英雄们的个人信息。每个英雄都需要一份工作。
|
||||
公司的任务就是让适当的英雄去解决它/她所擅长应对的危机!
|
||||
公司的使命就是让合适的英雄去应对恰当的危机!
|
||||
|
||||
Two of the three fields on this form are required. Required fields have a green bar on the left to make them easy to spot.
|
||||
|
||||
|
@ -877,7 +877,7 @@ Imagine an application that helps the _Hero Employment Agency_ run its business.
|
||||
Heroes need work and the agency finds crises for them to solve.
|
||||
|
||||
假设本程序会用来帮助“英雄管理局”运行他们的业务。
|
||||
英雄们需要找工作,而“英雄管理局”为它们寻找待解决的危机。
|
||||
英雄们需要找工作,而“英雄管理局”为他们寻找待解决的危机。
|
||||
|
||||
The application has three main feature areas:
|
||||
|
||||
@ -2057,7 +2057,7 @@ The heroes feature has two interacting components, the hero list and the hero de
|
||||
The list view is self-sufficient; you navigate to it, it gets a list of heroes and displays them.
|
||||
|
||||
“英雄”特性有两个相互协作的组件,列表和详情。
|
||||
列表视图是自给自足的,我们导航到它,它会自行获取英雄列表并显示它们。
|
||||
列表视图是自给自足的,我们导航到它,它会自行获取英雄列表并显示他们。
|
||||
|
||||
The detail view is different. It displays a particular hero. It can't know which hero to show on its own.
|
||||
That information must come from outside.
|
||||
@ -4657,7 +4657,7 @@ You could hide the link until the user logs in. But that's tricky and difficult
|
||||
Instead you'll write a `canActivate()` guard method to redirect anonymous users to the
|
||||
login page when they try to enter the admin area.
|
||||
|
||||
我们换种方式:写一个`CanActivate()`守卫,当匿名用户尝试访问管理组件时,把它/她重定向到登录页。
|
||||
我们换种方式:写一个`CanActivate()`守卫,将正在尝试访问管理组件匿名用户重定向到登录页。
|
||||
|
||||
This is a general purpose guard—you can imagine other features
|
||||
that require authenticated users—so you create an
|
||||
|
@ -2777,7 +2777,7 @@ Most, if not all, are previously displayed heroes.
|
||||
But Angular sees only a fresh list of new object references.
|
||||
It has no choice but to tear down the old DOM elements and insert all new DOM elements.
|
||||
|
||||
它们中的绝大多数(如果不是所有的话)都是以前显示过的英雄。*我们*知道这一点,是因为每个英雄的`id`没有变化。
|
||||
他们中的绝大多数(如果不是所有的话)都是以前显示过的英雄。*我们*知道这一点,是因为每个英雄的`id`没有变化。
|
||||
但在 Angular 看来,它只是一个由新的对象引用构成的新列表,
|
||||
它没有选择,只能清理旧列表、舍弃那些 DOM 元素,并且用新的 DOM 元素来重建一个新列表。
|
||||
|
||||
|
@ -413,5 +413,5 @@ You'll also allow the user to select heroes and display their details.
|
||||
You'll learn more about how to retrieve lists and bind them to the template.
|
||||
|
||||
在[教程的下一章](tutorial/toh-pt2),我们将在这个《英雄指南》中显示一个英雄列表。
|
||||
我们将允许允许用户选择一个英雄,并且显示它/她的详情。
|
||||
我们将允许允许用户选择英雄,并显示他们的详情。
|
||||
我们还将学会如何获取列表以及将它们绑定到模板中。
|
||||
|
@ -710,7 +710,7 @@ The callback sets the component's `heroes` property to the array of heroes retur
|
||||
The app is still running, showing a list of heroes, and
|
||||
responding to a name selection with a detail view.
|
||||
|
||||
我们的程序仍在运行,仍在显示英雄列表,在选择英雄时,仍然会把它/她显示在详情页面中。
|
||||
程序仍在运行,显示英雄列表,在选择英雄姓名时,会在详情视图中显示英雄的信息。
|
||||
|
||||
|
||||
<div class="l-sub-section">
|
||||
|
@ -821,7 +821,7 @@ Create that file with this content:
|
||||
`*ngFor` is used again to iterate over a list of heroes and display their names.
|
||||
The extra `<div>` elements will help with styling later.
|
||||
|
||||
我们再次使用`*ngFor`来在英雄列表上迭代,并显示它们的名字。
|
||||
我们再次使用`*ngFor`来在英雄列表上迭代,并显示他们的名字。
|
||||
还添加了一个额外的`<div>`元素,来帮助稍后的美化工作。
|
||||
|
||||
### Sharing the *HeroService*
|
||||
|
Loading…
x
Reference in New Issue
Block a user