338 lines
22 KiB
Markdown
338 lines
22 KiB
Markdown
# Introduction to components
|
||
|
||
A *component* controls a patch of screen called a *view*.
|
||
For example, individual components define and control each of the following views from the [Tutorial](tutorial):
|
||
|
||
*组件*控制屏幕上被称为*视图*的一小片区域。比如，[教程](tutorial/index)中的下列视图都是由一个个组件所定义和控制的：
|
||
|
||
* The app root with the navigation links.
|
||
|
||
带有导航链接的应用根组件。
|
||
|
||
* The list of heroes.
|
||
|
||
英雄列表。
|
||
|
||
* The hero editor.
|
||
|
||
英雄编辑器。
|
||
|
||
You define a component's application logic—what it does to support the view—inside a class.
|
||
The class interacts with the view through an API of properties and methods.
|
||
|
||
你在类中定义组件的应用逻辑，为视图提供支持。
|
||
组件通过一些由属性和方法组成的 API 与视图交互。
|
||
|
||
For example, `HeroListComponent` has a `heroes` property that holds an array of heroes.
|
||
Its `selectHero()` method sets a `selectedHero` property when the user clicks to choose a hero from that list.
|
||
The component acquires the heroes from a service, which is a TypeScript [parameter property](http://www.typescriptlang.org/docs/handbook/classes.html#parameter-properties) on the constructor.
|
||
The service is provided to the component through the dependency injection system.
|
||
|
||
比如，`HeroListComponent` 有一个 `heroes` 属性，它会返回一个从服务中取到的英雄数组。
|
||
`HeroListComponent` 还有一个 `selectHero()` 方法，当用户从列表中选择一个英雄时，它会设置 `selectedHero` 属性的值。
|
||
该组件会从服务获取英雄列表，它是一个 TypeScript 的构造器[参数型属性](http://www.typescriptlang.org/docs/handbook/classes.html#parameter-properties)。本服务通过依赖注入系统提供给该组件。
|
||
|
||
<code-example path="architecture/src/app/hero-list.component.ts" linenums="false" header="src/app/hero-list.component.ts (class)" region="class"></code-example>
|
||
|
||
Angular creates, updates, and destroys components as the user moves through the application. Your app can take action at each moment in this lifecycle through optional [lifecycle hooks](guide/lifecycle-hooks), like `ngOnInit()`.
|
||
|
||
当用户在应用中穿行时，Angular 就会创建、更新、销毁一些组件。
|
||
你的应用可以通过一些可选的[生命周期钩子](guide/lifecycle-hooks)（比如`ngOnInit()`）来在每个特定的时机采取行动。
|
||
|
||
## Component metadata
|
||
|
||
## 组件的元数据
|
||
|
||
<img src="generated/images/guide/architecture/metadata.png" alt="Metadata" class="left">
|
||
|
||
The `@Component` decorator identifies the class immediately below it as a component class, and specifies its metadata. In the example code below, you can see that `HeroListComponent` is just a class, with no special Angular notation or syntax at all. It's not a component until you mark it as one with the `@Component` decorator.
|
||
|
||
`@Component` 装饰器会指出紧随其后的那个类是个组件类，并为其指定元数据。
|
||
在下面的范例代码中，你可以看到 `HeroListComponent` 只是一个普通类，完全没有 Angular 特有的标记或语法。
|
||
直到给它加上了 `@Component` 装饰器，它才变成了组件。
|
||
|
||
The metadata for a component tells Angular where to get the major building blocks that it needs to create and present the component and its view. In particular, it associates a *template* with the component, either directly with inline code, or by reference. Together, the component and its template describe a *view*.
|
||
|
||
组件的元数据告诉 Angular 到哪里获取它需要的主要构造块，以创建和展示这个组件及其视图。
|
||
具体来说，它把一个*模板*（无论是直接内联在代码中还是引用的外部文件）和该组件关联起来。
|
||
该组件及其模板，共同描述了一个*视图*。
|
||
|
||
In addition to containing or pointing to the template, the `@Component` metadata configures, for example, how the component can be referenced in HTML and what services it requires.
|
||
|
||
除了包含或指向模板之外，`@Component` 的元数据还会配置要如何在 HTML 中引用该组件，以及该组件需要哪些服务等等。
|
||
|
||
Here's an example of basic metadata for `HeroListComponent`.
|
||
|
||
下面的例子中就是 `HeroListComponent` 的基础元数据：
|
||
|
||
<code-example path="architecture/src/app/hero-list.component.ts" linenums="false" header="src/app/hero-list.component.ts (metadata)" region="metadata"></code-example>
|
||
|
||
This example shows some of the most useful `@Component` configuration options:
|
||
|
||
这个例子展示了一些最常用的 `@Component` 配置选项：
|
||
|
||
* `selector`: A CSS selector that tells Angular to create and insert an instance of this component wherever it finds the corresponding tag in template HTML. For example, if an app's HTML contains `<app-hero-list></app-hero-list>`, then
|
||
Angular inserts an instance of the `HeroListComponent` view between those tags.
|
||
|
||
`selector`：是一个 CSS 选择器，它会告诉 Angular，一旦在模板 HTML 中找到了这个选择器对应的标签，就创建并插入该组件的一个实例。
|
||
比如，如果应用的 HTML 中包含 `<app-hero-list></app-hero-list>`，Angular 就会在这些标签中插入一个 `HeroListComponent` 实例的视图。
|
||
|
||
* `templateUrl`: The module-relative address of this component's HTML template. Alternatively, you can provide the HTML template inline, as the value of the `template` property. This template defines the component's *host view*.
|
||
|
||
`templateUrl`：该组件的 HTML 模板文件相对于这个组件文件的地址。
|
||
另外，你还可以用 `template` 属性的值来提供内联的 HTML 模板。
|
||
这个模板定义了该组件的*宿主视图*。
|
||
|
||
* `providers`: An array of [providers](guide/glossary#provider) for services that the component requires. In the example, this tells Angular how to provide the `HeroService` instance that the component's constructor uses to get the list of heroes to display.
|
||
|
||
`providers`：当前组件所需的服务[提供商](guide/glossary#provider)的一个数组。在这个例子中，它告诉 Angular 该如何提供一个 `HeroService` 实例，以获取要显示的英雄列表。
|
||
|
||
## Templates and views
|
||
|
||
## 模板与视图
|
||
|
||
<img src="generated/images/guide/architecture/template.png" alt="Template" class="left">
|
||
|
||
You define a component's view with its companion template. A template is a form of HTML that tells Angular how to render the component.
|
||
|
||
你要通过组件的配套模板来定义其视图。模板就是一种 HTML，它会告诉 Angular 如何渲染该组件。
|
||
|
||
Views are typically arranged hierarchically, allowing you to modify or show and hide entire UI sections or pages as a unit. The template immediately associated with a component defines that component's *host view*. The component can also define a *view hierarchy*, which contains *embedded views*, hosted by other components.
|
||
|
||
视图通常会分层次进行组织，让你能以 UI 分区或页面为单位进行修改、显示或隐藏。
|
||
与组件直接关联的模板会定义该组件的*宿主视图*。该组件还可以定义一个*带层次结构的视图*，它包含一些*内嵌的视图*作为其它组件的宿主。
|
||
|
||
<figure>
|
||
<img src="generated/images/guide/architecture/component-tree.png" alt="Component tree" class="left">
|
||
</figure>
|
||
|
||
A view hierarchy can include views from components in the same NgModule, but it also can (and often does) include views from components that are defined in different NgModules.
|
||
|
||
带层次结构的视图可以包含同一模块（NgModule）中组件的视图，也可以（而且经常会）包含其它模块中定义的组件的视图。
|
||
|
||
## Template syntax
|
||
|
||
## 模板语法
|
||
|
||
A template looks like regular HTML, except that it also contains Angular [template syntax](guide/template-syntax), which alters the HTML based on your app's logic and the state of app and DOM data. Your template can use *data binding* to coordinate the app and DOM data, *pipes* to transform data before it is displayed, and *directives* to apply app logic to what gets displayed.
|
||
|
||
模板很像标准的 HTML，但是它还包含 Angular 的[模板语法](guide/template-syntax)，这些模板语法可以根据你的应用逻辑、应用状态和 DOM 数据来修改这些 HTML。
|
||
你的模板可以使用*数据绑定*来协调应用和 DOM 中的数据，使用*管道*在显示出来之前对其进行转换，使用*指令*来把程序逻辑应用到要显示的内容上。
|
||
|
||
For example, here is a template for the Tutorial's `HeroListComponent`.
|
||
|
||
比如，下面是本教程中 `HeroListComponent` 的模板：
|
||
|
||
<code-example path="architecture/src/app/hero-list.component.html" header="src/app/hero-list.component.html"></code-example>
|
||
|
||
This template uses typical HTML elements like `<h2>` and `<p>`, and also includes Angular template-syntax elements, `*ngFor`, `{{hero.name}}`, `(click)`, `[hero]`, and `<app-hero-detail>`. The template-syntax elements tell Angular how to render the HTML to the screen, using program logic and data.
|
||
|
||
这个模板使用了典型的 HTML 元素，比如 `<h2>` 和 `<p>`，还包括一些 Angular 的模板语法元素，如 `*ngFor`，`{{hero.name}}`，`click`、`[hero]` 和 `<app-hero-detail>`。这些模板语法元素告诉 Angular 该如何根据程序逻辑和数据在屏幕上渲染 HTML。
|
||
|
||
* The `*ngFor` directive tells Angular to iterate over a list.
|
||
|
||
`*ngFor` 指令告诉 Angular 在一个列表上进行迭代。
|
||
|
||
* `{{hero.name}}`, `(click)`, and `[hero]` bind program data to and from the DOM, responding to user input. See more about [data binding](#data-binding) below.
|
||
|
||
`{{hero.name}}`、`(click)` 和 `[hero]` 把程序数据绑定到及绑定回 DOM，以响应用户的输入。更多内容参见稍后的[数据绑定](#data-binding)部分。
|
||
|
||
* The `<app-hero-detail>` tag in the example is an element that represents a new component, `HeroDetailComponent`.
|
||
`HeroDetailComponent` (code not shown) defines the hero-detail child view of `HeroListComponent`.
|
||
Notice how custom components like this mix seamlessly with native HTML in the same layouts.
|
||
|
||
模板中的 `<app-hero-detail>` 标签是一个代表新组件 `HeroDetailComponent` 的元素。
|
||
`HeroDetailComponent`（代码略）定义了 `HeroListComponent` 的英雄详情子视图。
|
||
注意观察像这样的自定义组件是如何与原生 HTML 元素无缝的混合在一起的。
|
||
|
||
### Data binding
|
||
|
||
### 数据绑定
|
||
|
||
Without a framework, you would be responsible for pushing data values into the HTML controls and turning user responses into actions and value updates. Writing such push and pull logic by hand is tedious, error-prone, and a nightmare to read, as any experienced jQuery programmer can attest.
|
||
|
||
如果没有框架，你就要自己负责把数据值推送到 HTML 控件中，并把来自用户的响应转换成动作和对值的更新。
|
||
手动写这种数据推拉逻辑会很枯燥、容易出错，难以阅读 —— 用过 jQuery 的程序员一定深有体会。
|
||
|
||
Angular supports *two-way data binding*, a mechanism for coordinating the parts of a template with the parts of a component. Add binding markup to the template HTML to tell Angular how to connect both sides.
|
||
|
||
Angular 支持*双向数据绑定*，这是一种对模板中的各个部件与组件中的各个部件进行协调的机制。
|
||
往模板 HTML 中添加绑定标记可以告诉 Angular 该如何连接它们。
|
||
|
||
The following diagram shows the four forms of data binding markup. Each form has a direction: to the DOM, from the DOM, or both.
|
||
|
||
下图显示了数据绑定标记的四种形式。每种形式都有一个方向 —— 从组件到 DOM、从 DOM 到组件或双向。
|
||
|
||
<figure>
|
||
<img src="generated/images/guide/architecture/databinding.png" alt="Data Binding" class="left">
|
||
</figure>
|
||
|
||
This example from the `HeroListComponent` template uses three of these forms.
|
||
|
||
这个来自 `HeroListComponent` 模板中的例子使用了其中的三种形式：
|
||
|
||
<code-example path="architecture/src/app/hero-list.component.1.html" linenums="false" header="src/app/hero-list.component.html (binding)" region="binding"></code-example>
|
||
|
||
* The `{{hero.name}}` [*interpolation*](guide/displaying-data#interpolation)
|
||
displays the component's `hero.name` property value within the `<li>` element.
|
||
|
||
`{{hero.name}}`[*插值表达式*](guide/displaying-data#interpolation)在 `<li>` 标签中显示组件的 `hero.name` 属性的值。
|
||
|
||
* The `[hero]` [*property binding*](guide/template-syntax#property-binding) passes the value of
|
||
`selectedHero` from the parent `HeroListComponent` to the `hero` property of the child `HeroDetailComponent`.
|
||
|
||
`[hero]`[*属性绑定*](guide/template-syntax#property-binding)把父组件 `HeroListComponent` 的 `selectedHero` 的值传到子组件 `HeroDetailComponent` 的 `hero` 属性中。
|
||
|
||
* The `(click)` [*event binding*](guide/user-input#binding-to-user-input-events) calls the component's `selectHero` method when the user clicks a hero's name.
|
||
|
||
当用户点击某个英雄的名字时，`(click)` [*事件绑定*](guide/user-input#binding-to-user-input-events)会调用组件的 `selectHero` 方法。
|
||
|
||
Two-way data binding (used mainly in [template-driven forms](guide/forms))
|
||
combines property and event binding in a single notation.
|
||
Here's an example from the `HeroDetailComponent` template that uses two-way data binding with the `ngModel` directive.
|
||
|
||
**双向数据绑定**（主要用于[模板驱动表单](guide/forms)中），它会把属性绑定和事件绑定组合成一种单独的写法。下面这个来自 `HeroDetailComponent` 模板中的例子通过 `ngModel` 指令使用了双向数据绑定：
|
||
|
||
<code-example path="architecture/src/app/hero-detail.component.html" linenums="false" header="src/app/hero-detail.component.html (ngModel)" region="ngModel"></code-example>
|
||
|
||
In two-way binding, a data property value flows to the input box from the component as with property binding.
|
||
The user's changes also flow back to the component, resetting the property to the latest value,
|
||
as with event binding.
|
||
|
||
在双向绑定中，数据属性值通过属性绑定从组件流到输入框。用户的修改通过事件绑定流回组件，把属性值设置为最新的值。
|
||
|
||
Angular processes *all* data bindings once for each JavaScript event cycle,
|
||
from the root of the application component tree through all child components.
|
||
|
||
Angular 在每个 JavaScript 事件循环中处理*所有的*数据绑定，它会从组件树的根部开始，递归处理全部子组件。
|
||
|
||
<figure>
|
||
<img src="generated/images/guide/architecture/component-databinding.png" alt="Data Binding" class="left">
|
||
</figure>
|
||
|
||
Data binding plays an important role in communication between a template and its component, and is also important for communication between parent and child components.
|
||
|
||
数据绑定在模板及其组件之间的通讯中扮演了非常重要的角色，它对于父组件和子组件之间的通讯也同样重要。
|
||
|
||
<figure>
|
||
<img src="generated/images/guide/architecture/parent-child-binding.png" alt="Parent/Child binding" class="left">
|
||
</figure>
|
||
|
||
### Pipes
|
||
|
||
### 管道
|
||
|
||
Angular pipes let you declare display-value transformations in your template HTML. A class with the `@Pipe` decorator defines a function that transforms input values to output values for display in a view.
|
||
|
||
Angular 的管道可以让你在模板中声明显示值的转换逻辑。
|
||
带有 `@Pipe` 装饰器的类中会定义一个转换函数，用来把输入值转换成供视图显示用的输出值。
|
||
|
||
Angular defines various pipes, such as the [date](https://angular.io/api/common/DatePipe) pipe and [currency](https://angular.io/api/common/CurrencyPipe) pipe; for a complete list, see the [Pipes API list](https://angular.io/api?type=pipe). You can also define new pipes.
|
||
|
||
Angular 自带了很多管道，比如 [date](https://angular.cn/api/common/DatePipe) 管道和 [currency](https://angular.cno/api/common/CurrencyPipe) 管道，完整的列表参见 [Pipes API 列表](https://angular.cn/api?type=pipe)。你也可以自己定义一些新管道。
|
||
|
||
To specify a value transformation in an HTML template, use the [pipe operator (|)](https://angular.io/guide/template-syntax#pipe).
|
||
|
||
要在 HTML 模板中指定值的转换方式，请使用 [管道操作符 (|)](https://angular.cn/guide/template-syntax#pipe)。
|
||
|
||
`{{interpolated_value | pipe_name}}`
|
||
|
||
You can chain pipes, sending the output of one pipe function to be transformed by another pipe function. A pipe can also take arguments that control how it performs its transformation. For example, you can pass the desired format to the `date` pipe.
|
||
|
||
你可以把管道串联起来，把一个管道函数的输出送给另一个管道函数进行转换。
|
||
管道还能接收一些参数，来控制它该如何进行转换。比如，你可以把要使用的日期格式传给 `date` 管道：
|
||
|
||
```
|
||
<!-- Default format: output 'Jun 15, 2015'-->
|
||
|
||
<p>Today is {{today | date}}</p>
|
||
|
||
<!-- fullDate format: output 'Monday, June 15, 2015'-->
|
||
|
||
<p>The date is {{today | date:'fullDate'}}</p>
|
||
|
||
<!-- shortTime format: output '9:43 AM'-->
|
||
|
||
<p>The time is {{today | date:'shortTime'}}</p>
|
||
|
||
```
|
||
|
||
### Directives
|
||
|
||
### 指令
|
||
|
||
<img src="generated/images/guide/architecture/directive.png" alt="Directives" class="left">
|
||
|
||
Angular templates are *dynamic*. When Angular renders them, it transforms the DOM according to the instructions given by *directives*. A directive is a class with a `@Directive()` decorator.
|
||
|
||
Angular 的模板是*动态的*。当 Angular 渲染它们的时候，会根据*指令*给出的指示对 DOM 进行转换。
|
||
指令就是一个带有 `@Directive()` 装饰器的类。
|
||
|
||
A component is technically a directive.
|
||
However, components are so distinctive and central to Angular applications that Angular
|
||
defines the `@Component()` decorator, which extends the `@Directive()` decorator with
|
||
template-oriented features.
|
||
|
||
组件从技术角度上说就是一个指令，但是由于组件对 Angular 应用来说非常独特、非常重要，因此 Angular 专门定义了 `@Component()` 装饰器，它使用一些面向模板的特性扩展了 `@Directive()` 装饰器。
|
||
|
||
In addition to components, there are two other kinds of directives: *structural* and *attribute*.
|
||
Angular defines a number of directives of both kinds, and you can define your own using the `@Directive()` decorator.
|
||
|
||
除组件外，还有两种指令：*结构型指令*和*属性型指令*。
|
||
Angular 本身定义了一系列这两种类型的指令，你也可以使用 `@Directive()` 装饰器来定义自己的指令。
|
||
|
||
Just as for components, the metadata for a directive associates the decorated class with a `selector` element that you use to insert it into HTML. In templates, directives typically appear within an element tag as attributes, either by name or as the target of an assignment or a binding.
|
||
|
||
像组件一样，指令的元数据把它所装饰的指令类和一个 `selector` 关联起来，`selector` 用来把该指令插入到 HTML 中。
|
||
在模板中，指令通常作为属性出现在元素标签上，可能仅仅作为名字出现，也可能作为赋值目标或绑定目标出现。
|
||
|
||
#### Structural directives
|
||
|
||
#### 结构型指令
|
||
|
||
*Structural directives* alter layout by adding, removing, and replacing elements in the DOM.
|
||
The example template uses two built-in structural directives to add application logic to how the view is rendered.
|
||
|
||
*结构型指令*通过添加、移除或替换 DOM 元素来修改布局。
|
||
这个范例模板使用了两个内置的结构型指令来为要渲染的视图添加程序逻辑：
|
||
|
||
<code-example path="architecture/src/app/hero-list.component.1.html" linenums="false" header="src/app/hero-list.component.html (structural)" region="structural"></code-example>
|
||
|
||
* [`*ngFor`](guide/displaying-data#ngFor) is an iterative; it tells Angular to stamp out one `<li>` per hero in the `heroes` list.
|
||
|
||
[`*ngFor`](guide/displaying-data#ngFor) 是一个迭代器，它要求 Angular 为 `heroes` 列表中的每个 `<li>` 渲染出一个 `<li>`。
|
||
|
||
* [`*ngIf`](guide/displaying-data#ngIf) is a conditional; it includes the `HeroDetail` component only if a selected hero exists.
|
||
|
||
[`*ngIf`](guide/displaying-data#ngIf) 是个条件语句，只有当选中的英雄存在时，它才会包含 `HeroDetail` 组件。
|
||
|
||
#### Attribute directives
|
||
|
||
#### 属性型指令
|
||
|
||
*Attribute directives* alter the appearance or behavior of an existing element.
|
||
In templates they look like regular HTML attributes, hence the name.
|
||
|
||
*属性型指令*会修改现有元素的外观或行为。
|
||
在模板中，它们看起来就像普通的 HTML 属性一样，因此得名“属性型指令”。
|
||
|
||
The `ngModel` directive, which implements two-way data binding, is an example of an attribute directive. `ngModel` modifies the behavior of an existing element (typically `<input>`) by setting its display value property and responding to change events.
|
||
|
||
`ngModel` 指令就是属性型指令的一个例子，它实现了双向数据绑定。
|
||
`ngModel` 修改现有元素（一般是 `<input>`）的行为：设置其显示属性值，并响应 change 事件。
|
||
|
||
<code-example path="architecture/src/app/hero-detail.component.html" linenums="false" header="src/app/hero-detail.component.html (ngModel)" region="ngModel"></code-example>
|
||
|
||
Angular has more pre-defined directives that either alter the layout structure
|
||
(for example, [ngSwitch](guide/template-syntax#ngSwitch))
|
||
or modify aspects of DOM elements and components
|
||
(for example, [ngStyle](guide/template-syntax#ngStyle) and [ngClass](guide/template-syntax#ngClass)).
|
||
|
||
<div class="alert is-helpful">
|
||
|
||
Learn more in the [Attribute Directives](guide/attribute-directives) and [Structural Directives](guide/structural-directives) guides.
|
||
|
||
欲知详情，参见[属性型指令](guide/attribute-directives)和[结构型指令](guide/structural-directives)这两章。
|
||
|
||
</div>
|