86 KiB

Raw Blame History

NgModules

Angular模块 (NgModule)

NgModules help organize an application into cohesive blocks of functionality.

Angular 模块能帮你把应用组织成多个内聚的功能块。

An NgModule is a class adorned with the @NgModule decorator function. @NgModule takes a metadata object that tells Angular how to compile and run module code. It identifies the module's own components, directives, and pipes, making some of them public so external components can use them. @NgModule may add service providers to the application dependency injectors. And there are many more options covered here.

Angular 模块是带有 @NgModule 装饰器函数的_类_。 @NgModule接收一个元数据对象，该对象告诉 Angular 如何编译和运行模块代码。它标记出该模块_拥有_的组件、指令和管道，并把它们的一部分公开出去，以便外部组件使用它们。它可以向应用的依赖注入器中添加服务提供商。本章还会涉及到更多选项。

Before reading this page, read the The Root Module page, which introduces NgModules and the essentials of creating and maintaining a single root AppModule for the entire application.

请先阅读根模块一章，那里介绍过 Angular 模块，以及如何为整个应用创建和维护单一的根AppModule类。

This page covers NgModules in greater depth.

本章的解释更加详尽，正如下面的目录所示。

Live examples

在线例子

This page explains NgModules through a progression of improvements to a sample with a "Tour of Heroes" theme. Here's an index to live examples at key moments in the evolution of the sample:

本章通过一个基于《英雄指南》的渐进式例子解释了 Angular 的模块。这里是例子演化过程中一些关键节点的在线例子。

A minimal NgModule app

最小的 NgModule 应用
The first contact module

第一个联系人模块
The revised contact module

修改过的联系人模块
Just before adding SharedModule

添加 SharedModule 之前
The final version

最终版

Frequently asked questions (FAQs)

常见问题

This page covers NgModule concepts in a tutorial fashion.

本章涵盖了英雄指南下的 Angular 模块概念。

The companion NgModule FAQs guide offers answers to specific design and implementation questions. Read this page before reading those FAQs.

烹饪宝典中的 Angular 模块常见问题为一些与设计和实现有关的问题提供了答案。不过在阅读常见问题之前，要先阅读本章。

{@a angular-modularity}

Angular modularity

Angular 模块化

Modules are a great way to organize an application and extend it with capabilities from external libraries.

模块是组织应用和使用外部库扩展应用的最佳途径。

Many Angular libraries are modules (such as FormsModule, HttpModule, and RouterModule). Many third-party libraries are available as NgModules (such as Material Design, Ionic, AngularFire2).

很多 Angular 库都是模块，例如：FormsModule、HttpModule、RouterModule。很多第三方库也封装成了 Angular 模块，例如：Material Design、 Ionic、 AngularFire2。

NgModules consolidate components, directives, and pipes into cohesive blocks of functionality, each focused on a feature area, application business domain, workflow, or common collection of utilities.

Angular 模块把组件、指令和管道打包成内聚的功能块，每个模块聚焦于一个特性区域、业务领域、工作流或通用工具。

Modules can also add services to the application. Such services might be internally developed, such as the application logger. Services can come from outside sources, such as the Angular router and Http client.

模块还能用来把服务加到应用程序中。这些服务可能是内部研发的，例如应用日志服务；也可能是外部资源，例如 Angular 路由和 Http 客户端。

Modules can be loaded eagerly when the application starts. They can also be lazy loaded asynchronously by the router.

模块可能在应用启动时主动加载，也可能由路由器进行异步_惰性加载_。

An NgModule is a class decorated with @NgModule metadata. The metadata do the following:

Angular 模块是一个由@NgModule装饰器提供元数据的类，元数据包括：

Declare which components, directives, and pipes belong to the module.

声明哪些组件、指令、管道_属于_该模块。
Make some of those classes public so that other component templates can use them.

公开某些类，以便其它的组件模板可以使用它们。
Import other modules with the components, directives, and pipes needed by the components in this module.

导入其它模块，从其它模块中获得_本_模块所需的组件、指令和管道。
Provide services at the application level that any application component can use.

在应用程序级提供服务，以便应用中的任何组件都能使用它。

Every Angular app has at least one module class, the root module. You bootstrap that module to launch the application.

每个 Angular 应用至少有一个模块类 —— 根模块，我们将通过引导根模块来启动应用。

The root module is all you need in a simple application with a few components. As the app grows, you refactor the root module into feature modules that represent collections of related functionality. You then import these modules into the root module.

对于组件很少的简单应用来说，只用一个_根模块_就足够了。随着应用规模的增长，我们逐步从_根模块_中重构出一些特性模块，来代表一组相关功能的集合。然后，我们在_根模块_中导入它们。

Later in this page, you'll read about this process. For now, you'll start with the root module.

稍后我们就会看到怎么做。不过还是先从_根模块_开始吧！

{@a root-module}

The root AppModule

AppModule - 应用的根模块

Every Angular app has a root module class. By convention, the root module class is called AppModule and it exists in a file named app.module.ts.

每个 Angular 应用都有一个根模块类。按照约定，它的类名叫做AppModule，被放在app.module.ts文件中。

The AppModule from the QuickStart seed on the Setup page is as minimal as possible:

快速起步种子库中的AppModule是能找到的最小版本：

The @NgModule decorator defines the metadata for the module. This page takes an intuitive approach to understanding the metadata and fills in details as it progresses.

@NgModule装饰器用来为模块定义元数据。我们先凭直觉来理解一下元数据，接下来再逐步深入细节。

The metadata imports a single helper module, BrowserModule, which every browser app must import.

这个元数据只导入了一个辅助模块，BrowserModule，每个运行在浏览器中的应用都必须导入它。

BrowserModule registers critical application service providers. It also includes common directives like NgIf and NgFor, which become immediately visible and usable in any of this module's component templates.

BrowserModule注册了一些关键的应用服务提供商。它还包括了一些通用的指令，例如NgIf和NgFor，所以这些指令在该模块的任何组件模板中都是可用的。

The declarations list identifies the application's only component, the root component, the top of the app's rather bare component tree.

declarations列出了该应用程序中唯一的组件（根组件），它是应用的光秃秃的组件树的根。

The example AppComponent simply displays a data-bound title:

下面范例AppComponent显示被绑定的标题：

Lastly, the @NgModule.bootstrap property identifies this AppComponent as the bootstrap component. When Angular launches the app, it places the HTML rendering of AppComponent in the DOM, inside the <my-app> element tags of the index.html.

最后，@NgModule.bootstrap属性把这个AppComponent标记为_引导 (bootstrap) 组件_。当 Angular 引导应用时，它会在 DOM 中渲染AppComponent，并把结果放进index.html的<my-app>元素标记内部。

{@a bootstrap}

Bootstrapping in main.ts

在 main.ts 中引导

You launch the application by bootstrapping the AppModule in the main.ts file.

在main.ts文件中，我们通过引导AppModule来启动应用。

Angular offers a variety of bootstrapping options targeting multiple platforms. This page describes two options, both targeting the browser.

针对不同的平台，Angular 提供了很多引导选项。本章我们只讲两个选项，都是针对浏览器平台的。

Compile just-in-time (JIT)

即时 (JiT) 编译

In the first, dynamic option, the Angular compiler compiles the application in the browser and then launches the app.

先看看_动态_选项，Angular 编译器在浏览器中编译并引导该应用。

The samples in this page demonstrate the dynamic bootstrapping approach.

这里的例子演示进行动态引导的方法。

Try the live example.

试试在线例子。

Compile ahead-of-time (AOT)

使用预编译器 (AoT - Ahead-Of-Time) 进行静态引导

Consider the static alternative which can produce a much smaller application that launches faster, especially on mobile devices and high latency networks.

静态方案可以生成更小、启动更快的应用，建议优先使用它，特别是在移动设备或高延迟网络下。

In the static option, the Angular compiler runs ahead of time as part of the build process, producing a collection of class factories in their own files. Among them is the AppModuleNgFactory.

使用_静态_选项，Angular 编译器作为构建流程的一部分提前运行，生成一组类工厂。它们的核心就是AppModuleNgFactory。

The syntax for bootstrapping the pre-compiled AppModuleNgFactory is similar to the dynamic version that bootstraps the AppModule class.

引导预编译的AppModuleNgFactory的语法和动态引导AppModule类的方式很相似。

Because the entire application was pre-compiled, Angular doesn't ship the Angular compiler to the browser and doesn't compile in the browser.

由于整个应用都是预编译的，所以我们不用把 _Angular 编译器_一起发到浏览器中，也不用在浏览器中进行编译。

The application code downloaded to the browser is much smaller than the dynamic equivalent and it's ready to execute immediately. The performance boost can be significant.

下载到浏览器中的应用代码比动态版本要小得多，并且能立即执行。引导的性能可以得到显著提升。

Both the JIT and AOT compilers generate an AppModuleNgFactory class from the same AppModule source code. The JIT compiler creates that factory class on the fly, in memory, in the browser. The AOT compiler outputs the factory to a physical file that is imported here in the static version of main.ts.

无论是 JiT 还是 AoT 编译器都会从同一份AppModule源码中生成一个AppModuleNgFactory类。 JiT 编译器动态地在浏览器的内存中创建这个工厂类。 AoT 编译器把工厂输出成一个物理文件，也就是我们在静态版本main.ts中导入的那个。

In general, the AppModule should neither know nor care how it is bootstrapped.

通常，AppModule不必关心它是如何被引导的。

Although the AppModule evolves as the app grows, the bootstrap code in main.ts doesn't change. This is the last time you'll look at main.ts.

虽然AppModule会随着应用而演化，但是main.ts中的引导代码不会变。这将是我们最后一次关注main.ts了。

{@a declarations}

Declare directives and components

声明指令和组件

As the app evolves, the first addition is a HighlightDirective, an attribute directive that sets the background color of the attached element.

应用继续演进。首先加入的是HighlightDirective，一个属性型指令，它会设置所在元素的背景色。

Update the AppComponent template to attach the directive to the title:

我们更新AppComponent的模板，来把该指令附加到标题上：

If you ran the app now, Angular wouldn't recognize the highlight attribute and would ignore it. You must declare the directive in AppModule.

如果我们现在就运行该应用，Angular 将无法识别highlight属性，并且忽略它。我们必须在AppModule中声明该指令。

Import the HighlightDirective class and add it to the module's declarations like this:

导入HighlightDirective类，并把它加入该模块的declarations数组中，就像这样：

Refactor the title into its own TitleComponent. The component's template binds to the component's title and subtitle properties like this:

接着把标题重构到独立的TitleComponent中。该组件的模板绑定到了组件的title和subtitle属性中，就像这样：

Rewrite the AppComponent to display the new TitleComponent in the <app-title> element, using an input binding to set the subtitle.

我们重写了AppComponent来把这个新的TitleComponent显示到<app-title>元素中，并使用一个输入型绑定来设置subtitle。

Angular won't recognize the <app-title> tag until you declare it in AppModule. Import the TitleComponent class and add it to the module's declarations:

除非我们在AppModule中声明过，否则 Angular 无法识别<app-title>标签。导入TitleComponent类，并把它加到模块的declarations中：

{@a providers}

Service providers

服务提供商

Modules are a great way to provide services for all of the module's components.

模块是为模块中的所有组件提供服务的最佳途径。

The Dependency Injection page describes the Angular hierarchical dependency-injection system and how to configure that system with providers at different levels of the application's component tree.

依赖注入一章中讲过 Angular 的层次化依赖注入系统，以及如何在组件树的不同层次上通过提供商配置该系统。

A module can add providers to the application's root dependency injector, making those services available everywhere in the application.

模块可以往应用的“根依赖注入器”中添加提供商，让那些服务在应用中到处可用。

Many applications capture information about the currently logged-in user and make that information accessible through a user service. This sample application has a dummy implementation of such a UserService.

很多应用都需要获取当前登录的用户的信息，并且通过一个用户服务来访问它们。该范例中有一个UserService的伪实现。

The sample application should display a welcome message to the logged-in user just below the application title. Update the TitleComponent template to show the welcome message below the application title.

该范例应用会在标题下方为已登录用户显示一条欢迎信息。更新TitleComponent的模板来显示它。

Update the TitleComponent class with a constructor that injects the UserService and sets the component's user property from the service.

更新TitleComponent，为它加入一个构造函数，注入UserService类，并把组件的user属性设置为它的实例。

You've defined and used the service. Now to provide it for all components to use, add it to a providers property in the AppModule metadata:

我们已经_定义_并_使用了_该服务。现在，我们通过把它加入AppModule元数据的providers属性中，来把它_提供_给所有组件使用。

{@a imports}

Import supporting modules

导入支持性模块

In the revised TitleComponent, an *ngIf directive guards the message. There is no message if there is no user.

注意，在修改过的TitleComponent中，有一个*ngIf指令在“守卫着”该消息。如果没有当前用户，就没有任何消息。

Although AppModule doesn't declare NgIf, the application still compiles and runs. How can that be? The Angular compiler should either ignore or complain about unrecognized HTML.

虽然AppModule没有声明过NgIf指令，但该应用仍然能正常编译和运行。为什么这样没问题呢？Angular 的编译器遇到不认识的 HTML 时应该不是忽略就是报错才对。

Angular does recognize NgIf because you imported it earlier. The initial version of AppModule imports BrowserModule.

Angular 能识别NgIf指令，是因为我们以前导入过它。最初版本的AppModule就导入了BrowserModule。

Importing BrowserModule made all of its public components, directives, and pipes visible to the component templates in AppModule.

导入BrowserModule会让该模块公开的所有组件、指令和管道在AppModule下的任何组件模板中可用。

More accurately, NgIf is declared in CommonModule from @angular/common.

更准确的说，NgIf是在来自@angular/common的CommonModule中声明的。

CommonModule contributes many of the common directives that applications need, including ngIf and ngFor.

CommonModule提供了很多应用程序中常用的指令，包括NgIf和NgFor等。

BrowserModule imports CommonModule and re-exports it. The net effect is that an importer of BrowserModule gets CommonModule directives automatically.

BrowserModule导入了CommonModule并且重新导出了它。最终的效果是：只要导入BrowserModule就自动获得了CommonModule中的指令。

Many familiar Angular directives don't belong to CommonModule. For example, NgModel and RouterLink belong to Angular's FormsModule and RouterModule respectively. You must import those modules before you can use their directives.

很多熟悉的 Angular 指令并不属于CommonModule。例如，NgModel和RouterLink分别属于 Angular 的FormsModule模块和RouterModule模块。在使用那些指令之前，我们也必须_导入_那些模块。

To illustrate this point, you'll extend the sample app with ContactComponent, a form component that imports form support from the Angular FormsModule.

要解释这一点，我们可以再加入ContactComponent组件，它是一个表单组件，从 Angular 的FormsModule中导入了表单支持。

Add the _ContactComponent_

添加 _ContactComponent_

Angular forms are a great way to manage user data entry.

Angular 表单是用来管理用户数据输入的最佳方式之一。

The ContactComponent presents a "contact editor," implemented with Angular forms in the template-driven form style.

ContactComponnet组件展现“联系人编辑器”，它是用模板驱动式表单实现的。

Angular form styles

Angular 表单的风格

You can write Angular form components in template-driven or reactive style.

我们写 Angular 表单组件时，可以使用模板驱动式表单，也可以使用响应式表单。

The following sample imports the FormsModule from @angular/forms because the ContactComponent is written in template-driven style. Modules with components written in the reactive style import the ReactiveFormsModule.

该例子中从@angular/forms中导入了FormsModule，这是因为ContactComponent组件用的是_模板驱动式表单_。那些带有_响应式表单_组件的模块，应该转而导入ReactiveFormsModule。

The ContactComponent selector matches an element named <app-contact>. Add an element with that name to the AppComponent template, just below the <app-title>:

ContactComponent的选择器会去匹配名叫<app-contact>的元素。在AppComponent模板中<app-title>的下方添加一个具有此名字的元素：

Form components are often complex. The ContactComponent has its own ContactService and custom pipe (called Awesome), and an alternative version of the HighlightDirective.

ContactComponent还有很多事要做。表单组件通常都是很复杂的。本组件具有它自己的ContactService和自定义管道 Awesome，以及HighlightDirective的另一个版本。

To make it manageable, place all contact-related material in an src/app/contact folder and break the component into three constituent HTML, TypeScript, and css files:

为了方便管理，我们把所有与联系人相关的编程元素都放进src/app/contact目录，并把该组件分解成三个基本成分：HTML、TypeScript 和 CSS 文件：

In the middle of the component template, notice the two-way data binding [(ngModel)]. ngModel is the selector for the NgModel directive.

先来看组件模板。注意模板中部的双向数据绑定[(ngModel)]。 ngModel是NgModel指令的选择器。

Although NgModel is an Angular directive, the Angular compiler won't recognize it for the following reasons:

虽然NgModel是 Angular 指令，但 _Angular 编译器_并不会识别它，因为：

AppModule doesn't declare NgModel.

AppModule没有声明过这个NgModel。
NgModel wasn't imported via BrowserModule.

NgModel也没有通过BrowserModule被导入过。

Even if Angular somehow recognized ngModel, ContactComponent wouldn't behave like an Angular form because form features such as validation aren't yet available.

退一步说，即使 Angular 有办法识别ngModel，ContactComponent也不会表现的像 Angular 表单，因为本组件表单的表单相关的特性（例如有效性验证）还不可用。

Import the FormsModule

导入 FormsModule

导入`FormsModule`

Add the FormsModule to the AppModule metadata's imports list.

把FormsModule加到AppModule元数据中的imports列表中：

Now [(ngModel)] binding will work and the user input will be validated by Angular forms, once you declare the new component, pipe, and directive.

一旦我们声明了这些新组件、管道和指令，[(ngModel)]绑定就会正常工作，用户的输入也能被 Angular 表单验证了。

Do not add NgModel—or the FORMS_DIRECTIVES—to the AppModule metadata's declarations. These directives belong to the FormsModule.

不要把NgModel（或FORMS_DIRECTIVES）加到AppModule元数据的declarations数据中！这些指令属于FormsModule`。

Components, directives, and pipes belong to one module only.

组件、指令和管道_只能_属于一个模块。

Never re-declare classes that belong to another module.

永远不要再次声明属于其它模块的类。

{@a declare-pipe}

Declare the contact component, directive, and pipe

声明联系人的组件、指令和管道

The application won't compile until you declare the contact component, directive, and pipe. Update the declarations in the AppModule accordingly:

如果我们没有声明该联系人模块的组件、指令和管道，该应用就会失败。更新AppModule中的declarations元数据，就像这样：

{@a import-name-conflict}

There are two directives with the same name, both called HighlightDirective.

如果有两个同名指令，都叫做HighlightDirective，该怎么办呢？

To work around this, create an alias for the contact version using the as JavaScript import keyword.

我们只要在 import 时使用as关键字来为第二个指令创建个别名就可以了。

This solves the immediate issue of referencing both directive types in the same file but leaves another issue unresolved. You'll learn more about that issue later in this page, in Resolve directive conflicts.

这解决了在文件中使用指令_类型_时的冲突问题，但是还有另一个问题没有解决，我们将在后面讨论它。

Provide the _ContactService_

提供 _ContactService_

The ContactComponent displays contacts retrieved by the ContactService, which Angular injects into its constructor.

ContactComponent显示从ContactService服务中获取的联系人信息，该服务是被 Angular 注入到组件的构造函数中的。

You have to provide that service somewhere. The ContactComponent could provide it, but then the service would be scoped to this component only. You want to share this service with other contact-related components that you'll surely add later.

我们必须在某个地方提供该服务。在ContactComponent中_可以_提供它。但是那样一来，它的作用范围就会_仅_局限于该组件及其子组件。而我们希望让该服务与其它和联系人有关的组件中共享，稍后我们就会添加那些组件。

In this app, add ContactService to the AppModule metadata's providers list:

在此应用中，我们选择把ContactSerivce添加到AppModule元数据的providers列表中：

Now you can inject ContactService (like UserService) into any component in the application.

现在，ContactService服务就能被注入进该应用中的任何组件了，就像UserService一样。

{@a application-scoped-providers}

Application-scoped providers

全应用范围的提供商

The ContactService provider is application-scoped because Angular registers a module's providers with the application's root injector.

ContactService的提供商是_全应用_范围的，这是因为 Angular 使用该应用的根注入器注册模块的providers。

Architecturally, the ContactService belongs to the Contact business domain. Classes in other domains don't need the ContactService and shouldn't inject it.

从架构上看，ContactService属于“联系人”这个业务领域。 _其它_领域中的类并不需要知道ContactService，也不会要求注入它。

You might expect Angular to offer a module-scoping mechanism to enforce this design. It doesn't. NgModule instances, unlike components, don't have their own injectors so they can't have their own provider scopes.

我们可能会期待 Angular 提供一种_模块_范围内的机制来保障此设计。但它没有。与组件不同，Angular的模块实例并没有它们自己的注入器，所以它们也没有自己的供应商范围。

This omission is intentional. NgModules are designed primarily to extend an application, to enrich the entire app with the module's capabilities.

Angular是故意这么设计的。 Angular的模块设计，主要目的是扩展应用程序，丰富其模块化能力。

In practice, service scoping is rarely an issue. Non-contact components can't accidentally inject the ContactService. To inject ContactService, you must first import its type. Only Contact components should import the ContactService type.

在实践中，服务的范围很少会成为问题。联系人之外的组件不会意外注入ContactService服务。要想注入ContactService，你得先导入它的_类型_。而只有联系人组件才会导入ContactService类型。

Read more in the How do I restrict service scope to a module? section of the NgModule FAQs page.

在NgModule常见问题页的如何把服务的范围限制在一个模块中一节中可以了解更多。

Run the app

运行该应用

Everything is in place to run the application with its contact editor.

一切就绪，可以运行该应用及其联系人编辑器了。

The app file structure looks like this:

应用的文件结构是这样的：

app

<div class='file'>
  app.component.ts
</div>

<div class='file'>
  app.module.ts
</div>

<div class='file'>
  highlight.directive.ts
</div>

<div class='file'>
  title.component.(html|ts)
</div>

<div class='file'>
  user.service.ts
</div>

<div class='file'>
  contact
</div>

<div class='children'>

  <div class='file'>
    awesome.pipe.ts
  </div>

  <div class='file'>
    contact.component.(css|html|ts)
  </div>

  <div class='file'>
    contact.service.ts
  </div>

  <div class='file'>
    highlight.directive.ts
  </div>

</div>

Try the example: 试试这个例子：

{@a resolve-conflicts}

Resolve directive conflicts

解决指令冲突

An issue arose earlier when you declared the contact's HighlightDirective because you already had a HighlightDirective class at the application level.

以前我们在声明联系人的HighlightDirective指令时遇到了问题，因为在应用程序一级已经有了一个HighlightDirective类。

The selectors of the two directives both highlight the attached element with a different color.

在查找它们的选择器时，它们都试图用不同的颜色来高亮所依附的元素。

Both directives are declared in this module so both directives are active.

Angular 会只用它们中的一个吗？不会。所有指令都声明在该模块中，所以_这两个指令都会被激活_。

When the two directives compete to color the same element, the directive that's declared later wins because its DOM changes overwrite the first. In this case, the contact's HighlightDirective makes the application title text blue when it should stay gold.

当两个指令在同一个元素上争相设置颜色时，后声明的那个会胜出，因为它对 DOM 的修改覆盖了前一个。在该例子中，联系人的HighlightDirective把应用标题的文本染成了蓝色，而我们原本期望它保持金色。

The issue is that two different classes are trying to do the same thing.

真正的问题在于，有_两个不同的类_试图做同一件事。

It's OK to import the same directive class multiple times. Angular removes duplicate classes and only registers one of them.

多次导入_同一个_指令是没问题的，Angular 会移除重复的类，而只注册一次。

But from Angular's perspective, two different classes, defined in different files, that have the same name are not duplicates. Angular keeps both directives and they take turns modifying the same HTML element.

从 Angular 的角度看，两个类并没有重复。Angular 会同时保留这两个指令，并让它们依次修改同一个 HTML 元素。

At least the app still compiles. If you define two different component classes with the same selector specifying the same element tag, the compiler reports an error. It can't insert two components in the same DOM location.

至少，应用仍然编译通过了。如果我们使用相同的选择器定义了两个不同的组件类，并指定了同一个元素标记，编译器就会报错说它无法在同一个 DOM 位置插入两个不同的组件。

To eliminate component and directive conflicts, create feature modules that insulate the declarations in one module from the declarations in another.

我们可以通过创建特性模块来消除组件与指令的冲突。特性模块可以把来自一个模块中的声明和来自另一个的区隔开。

{@a feature-modules}

Feature modules

特性模块

This application isn't big yet, but it's already experiencing structural issues.

该应用还不大，但是已经在受结构方面的问题困扰了。

The root AppModule grows larger with each new application class.

随着一个个类被加入应用中，根模块AppModule变大了。
There are conflicting directives. The HighlightDirective in the contact re-colors the work done by the HighlightDirective declared in AppModule. Also, it colors the application title text when it should color only the ContactComponent.

我们遇到了指令冲突。联系人模块的HighlightDirective在AppModule中声明的HighlightDirective的基础上进行了二次上色。并且，它染了应用标题文字的颜色，而不仅仅是ContactComponent中的。
The app lacks clear boundaries between contact functionality and other application features. That lack of clarity makes it harder to assign development responsibilities to different teams.

该应用在联系人和其它特性区之间缺乏清晰的边界。这种缺失，导致难以在不同的开发组之间分配职责。

You can resolve these issues with feature modules.

我们用_特性模块_技术来缓解此问题。

A feature module is a class adorned by the @NgModule decorator and its metadata, just like a root module. Feature module metadata have the same properties as the metadata for a root module.

_特性模块_是带有@NgModule装饰器及其元数据的类，就像根模块一样。特性模块的元数据和根模块的元数据的属性是一样的。

The root module and the feature module share the same execution context. They share the same dependency injector, which means the services in one module are available to all.

根模块和特性模块还共享着相同的执行环境。它们共享着同一个依赖注入器，这意味着某个模块中定义的服务在所有模块中也都能用。

The modules have the following significant technical differences:

它们在技术上有两个显著的不同点：

You boot the root module to launch the app; you import a feature module to extend the app.

我们_引导_根模块来_启动_应用，但_导入_特性模块来_扩展_应用。
A feature module can expose or hide its implementation from other modules.

特性模块可以对其它模块暴露或隐藏自己的实现。

Otherwise, a feature module is distinguished primarily by its intent.

此外，特性模块主要还是从它的设计意图上来区分。

A feature module delivers a cohesive set of functionality focused on an application business domain, user workflow, facility (forms, http, routing), or collection of related utilities.

特性模块用来提供了内聚的功能集合。聚焦于应用的某个业务领域、用户工作流、某个基础设施（表单、HTTP、路由），或一组相关的工具集合。

While you can do everything within the root module, feature modules help you partition the app into areas of specific interest and purpose.

虽然这些都能在根模块中做，但特性模块可以帮助我们把应用切分成具有特定关注点和目标的不同区域。

A feature module collaborates with the root module and with other modules through the services it provides and the components, directives, and pipes that it shares.

特性模块通过自己提供的服务和它决定对外共享的那些组件、指令、管道来与根模块等其它模块协同工作。

In the next section, you'll carve the contact functionality out of the root module and into a dedicated feature module.

下一节，我们从根模块中把与联系人有关的功能切分到专门的特性模块中。

{@a contact-module-v1}

Make Contact a feature module

把_联系人_做成特性模块

It's easy to refactor the contact material into a contact feature module.

把与联系人有关的这些元素重构到“联系人”特性模块中很简单。

Create the ContactModule in the src/app/contact folder.

在src/app/contact目录下创建ContactModule。
Move the contact material from AppModule to ContactModule.

把联系人相关的元素从AppModule移到ContactModule中。
Replace the imported BrowserModule with CommonModule.

把导入BrowserModule改为导入CommonModule。
Import the ContactModule into the AppModule.

在AppModule中导入ContactModule。

AppModule is the only existing class that changes. But you do add one new file.

AppModule是唯一有改变的_已经存在_的类，不过我们还会添加一个新文件。

Add the ContactModule

添加 ContactModule

Here's the new ContactModule:

下面是新的ContactModule：

You copy from AppModule the contact-related import statements and @NgModule properties that concern the contact, and paste them into ContactModule.

把AppModule中的相关联系人的 import 语句和@NgModule的相关属性复制到ContactModule。

You import the FormsModule because the contact component needs it.

导入FormsModule，因为联系人组件需要它。

Modules don't inherit access to the components, directives, or pipes that are declared in other modules. What AppModule imports is irrelevant to ContactModule and vice versa. Before ContactComponent can bind with [(ngModel)], its ContactModule must import FormsModule.

当前模块不会继承其它模块中对组件、指令或管道的访问权。 AppModule中的 imports 与ContatModule的 imports 互不相干。如果ContactComponent要绑定到[(ngModel)]，它所在的ContactModule必需导入FormsModule。

You also replaced BrowserModule by CommonModule, for reasons explained in the Should I import BrowserModule or CommonModule? section of the NgModule FAQs page.

我们还用CommonModule替换了BrowserModule，其中缘由参见这条常见问题。

You declare the contact component, directive, and pipe in the module declarations.

我们在该模块的declarations中声明了联系人组件、指令和管道。

You export the ContactComponent so other modules that import the ContactModule can include it in their component templates.

我们导出了ContactComponent，这样其它模块只要导入了ContactModule，就可以在它们的组件模板中使用ContactComponent了。

All other declared contact classes are private by default. The AwesomePipe and HighlightDirective are hidden from the rest of the application. The HighlightDirective can no longer color the AppComponent title text.

声明的所有其它联系人类默认都是私有的。 AwesomePipe和HighlightDirective对应用的其它部分是不可见的。所以HighlightDirective不能把AppComponent的标题文字染色。

Refactor the AppModule

重构 AppModule

Return to the AppModule and remove everything specific to the contact feature set.

返回AppModule并移除专属于联系人特性下的任何东西。

Delete the contact import statements.

删除属于联系人的import语句。
Delete the contact declarations and contact providers.

删除联系人的declarations和providers。
Delete the FormsModule from the imports list (AppComponent doesn't need it).

从imports列表中移除FormsModule（AppComponent并不需要它）。

Leave only the classes required at the application root level.

只保留本应用的根一级需要的那些类。

Then import the ContactModule so the app can continue to display the exported ContactComponent.

然后，导入ContactModule，以便应用能够继续显示导出的ContactComponent。

Here's the refactored version of the AppModule along with the previous version.

下面是AppModule重构完的版本与之前版本的对比。

Improvements

改进之处

There's a lot to like in the revised AppModule.

修改后的AppModule有一些很棒的特性。

It does not change as the Contact domain grows.

它不会再随着_联系人_的领域扩张而修改。
It only changes when you add new modules.

只有当添加新模块时才需要修改它。
It's simpler:

它也变得简单了：
- Fewer import statements.
  
  更少的import语句
- No FormsModule import.
  
  不再导入FormsModule
- No contact-specific declarations.
  
  没有与联系人有关的声明
- No ContactService provider.
  
  没有ContactService提供商
- No HighlightDirective conflict.
  
  没有HighlightDirective冲突

Try this ContactModule version of the sample.

试试范例的ContactModule版。

Try the live example.

试试在线例子

{@a lazy-load}

Lazy-loading modules with the router

用路由器实现惰性 (lazy) 加载

The Heroic Staffing Agency sample app has evolved. It has two more modules, one for managing the heroes on staff and another for matching crises to the heroes. Both modules are in the early stages of development. Their specifics aren't important to the story and this page doesn't discuss every line of code.

英雄职介所这个例子应用继续成长。它又增加了两个模块，一个用来管理雇佣的英雄，另一个用来匹配英雄与危机。这两个模块都还处于前期开发阶段。它们对于整个故事来说无关紧要，这里我们就不逐行讨论了。

Examine and download the complete source for this version from the live example.

到在线例子试用并下载当前版本的完整代码。

Some facets of the current application merit discussion are as follows:

当前应用中还有一些方面值得深入探讨。

The app has three feature modules: Contact, Hero, and Crisis.

该应用有三个特性模块：联系人 (Contact) 、英雄 (Hero) 和危机 (Crisis) 。
The Angular router helps users navigate among these modules.

Angular 路由器帮助用户在这些模块之间导航。
The ContactComponent is the default destination when the app starts.

ContactComponent组件是应用启动时的默认页。
The ContactModule continues to be "eagerly" loaded when the application starts.

ContactModule仍然会在应用启动时被主动加载。
HeroModule and the CrisisModule are lazy loaded.

HeroModule和CrisisModule会被惰性加载。

{@a app-component-template}

The new AppComponent templatehas a title, three links, and a <router-outlet>.

我们从这个AppComponent新模板的顶部看起：标题、三个链接和<router-outlet>。

The <app-contact> element is gone; you're routing to the Contact page now.

<app-contact>元素不见了，改成了路由到_联系人_页。

The AppModule has changed modestly:

对AppModule进行适度的修改：

Some file names bear a .3 extension that indicates a difference with prior or future versions. The significant differences will be explained in due course.

有些文件名带有.3扩展名，用来和以前/以后的版本区分开。我们会在适当的时机解释它们的差异。

The module still imports ContactModule so that its routes and components are mounted when the app starts.

该模块仍然要导入ContactModule模块，以便在应用启动时加载它的路由和组件。

The module does not import HeroModule or CrisisModule. They'll be fetched and mounted asynchronously when the user navigates to one of their routes.

该模块_不_导入HeroModule或CrisisModule。它们将在用户导航到其中的某个路由时，被异步获取并加载。

The significant change from version 2 is the addition of the AppRoutingModule to the module imports. The AppRoutingModule is a routing module that handles the app's routing concerns.

与第二版相比，最值得注意的修改是imports中那个额外的AppRoutingModule模块。 AppRoutingModule是一个路由模块 用来处理应用的路由。

App routing

应用路由

The router is the subject of the Routing & Navigation page, so this section skips many of the details and concentrates on the intersection of NgModules and routing.

路由器有专门的章节做深入讲解，所以这里我们跳过细节，而是专注于它和 Angular 模块的协作。

The app-routing.module.ts file defines three routes.

app-routing.module.ts文件定义了三个路由。

The first route redirects the empty URL (such as http://host.com/) to another route whose path is contact (such as http://host.com/contact).

第一个路由把空白 URL（例如http://host.com/）重定向到了另一个路径为contact的路由（例如http://host.com/contact）。

The contact route isn't defined here. It's defined in the Contact feature's own routing module, contact-routing.module.ts. It's standard practice for feature modules with routing components to define their own routes. You'll get to that file in a moment.

contact路由并不是在这里定义的，而是定义在联系人特性区自己的路由文件contact.routing.ts中。对于带有路由组件的特性模块，其标准做法就是让它们定义自己的路由。稍后我们就会看到这些。

The remaining two routes use lazy loading syntax to tell the router where to find the modules:

另外两个路由使用惰性加载语法来告诉路由器要到哪里去找这些模块。

A lazy-loaded module location is a string, not a type. In this app, the string identifies both the module file and the module class, the latter separated from the former by a #.

惰性加载模块的位置是字符串而不是类型。在本应用中，该字符串同时标记出了模块文件和模块类，两者用#分隔开。

RouterModule.forRoot

RouterModule.forRoot 方法

The forRoot static class method of the RouterModule with the provided configuration and added to the imports array provides the routing concerns for the module.

RouterModule类的forRoot静态方法和提供的配置，被添加到imports数组中，提供该模块的路由信息。

The returned AppRoutingModule class is a Routing Module containing both the RouterModule directives and the dependency-injection providers that produce a configured Router.

该方法返回的AppRoutingModule类是一个路由模块，它同时包含了RouterModule指令和用来生成配置好的Router的依赖注入提供商。

This AppRoutingModule is intended for the app root module only.

这个AppRoutingModule_仅_用于应用的_根_模块。

Never call RouterModule.forRoot in a feature-routing module.

永远不要在特性路由模块中调用RouterModule.forRoot！

Back in the root AppModule, add the AppRoutingModule to its imports list, and the app is ready to navigate.

回到根模块AppModule，把这个AppRoutingModule添加到根模块的imports列表中，该应用就可以正常导航了。

Routing to a feature module

路由到特性模块

The src/app/contact folder holds a new file, contact-routing.module.ts. It defines the contact route mentioned earlier and provides a ContactRoutingModule as follows:

src/app/contact目录中也有一个新文件contact-routing.module.ts。它定义了我们前面提到过的联系人路由，并提供了ContactRoutingModule，就像这样：

This time you pass the route list to the forChild method of the RouterModule. The route list is only responsible for providing additional routes and is intended for feature modules.

这次我们要把路由列表传给RouterModule的forChild方法。该方法会为特性模块生成另一种对象。

Always call RouterModule.forChild in a feature-routing module.

总是在特性路由模块中调用RouterModule.forChild。

forRoot and forChild are conventional names for methods that deliver different import values to root and feature modules. Angular doesn't recognize them but Angular developers do.

当需要为根模块和特性模块分别提供不同的导入值时，forRoot和forChild是约定俗成的方法名。虽然 Angular 无法识别它们，但是 Angular 开发人员可以。

Follow this convention if you write a similar module that has both shared declarables and services.

当你要写类似的模块，来为根模块和特性模块分别导出一些声明和服务时，请遵循这个约定。

ContactModule has changed in two small but important ways.

ContactModule已经做了两个微小但重要的细节改动：

It imports the ContactRoutingModule object from contact-routing.module.ts.

它从contact-routing.module.ts中导入了ContactRoutingModule对象
It no longer exports ContactComponent.

它不再导出ContactComponent

Now that you navigate to ContactComponent with the router, there's no reason to make it public. Also, ContactComponent doesn't need a selector. No template will ever again reference this ContactComponent. It's gone from the AppComponent template.

现在我们通过路由器导航到ContactComponent，所以也就没有理由公开它了。它也不再需要选择器 (selector)。也没有模板会再引用ContactComponent。它从 AppComponent 模板中彻底消失了。

{@a hero-module}

Lazy-loaded routing to a module

路由到惰性加载的模块

The lazy-loaded HeroModule and CrisisModule follow the same principles as any feature module. They don't look different from the eagerly loaded ContactModule.

惰性加载的HeroModule和CrisisModule与其它特性模块遵循同样的规则。它们和主动加载的ContactModule看上去没有任何区别。

The HeroModule is a bit more complex than the CrisisModule, which makes it a more interesting and useful example. Its file structure is as follows:

HeroModule比CrisisModule略复杂一些，因此更适合用作范例。它的文件结构如下：

hero

<div class='file'>
  hero-detail.component.ts
</div>

<div class='file'>
  hero-list.component.ts
</div>

<div class='file'>
  hero.component.ts
</div>

<div class='file'>
  hero.module.ts
</div>

<div class='file'>
  hero-routing.module.ts
</div>

<div class='file'>
  hero.service.ts
</div>

<div class='file'>
  highlight.directive.ts
</div>

This is the child routing scenario familiar to readers of the Child routing component section of the Routing & Navigation page. The HeroComponent is the feature's top component and routing host. Its template has a <router-outlet> that displays either a list of heroes (HeroList) or an editor of a selected hero (HeroDetail). Both components delegate to the HeroService to fetch and save data.

如果你读过路由那章，那么对这个子路由的场景应该觉得很熟悉。 HeroComponent是本特性区的顶级组件和路由宿主。模板带有<router-outlet>指令，它或者显示英雄列表（HeroList）或者显示所选英雄的编辑器（HeroDetail）。这两个组件都把获取和保存数据的任务委托给HeroService执行。

Yet another HighlightDirective colors elements in yet a different shade. In the next section, Shared modules, you'll resolve the repetition and inconsistencies.

还有另一个HighlightDirective指令，它用另一种方式为元素染色。在下一节的共享模块中，我们会解决这种不必要的重复和不一致性。

The HeroModule is a feature module like any other.

HeroModule是特性模块，与其它的没什么不同。

It imports the FormsModule because the HeroDetailComponent template binds with [(ngModel)]. It imports the HeroRoutingModule from hero-routing.module.ts just as ContactModule and CrisisModule do.

它导入了FormsModule，因为HeroDetailComponent的模板中绑定到了[(ngModel)]。像ContactModule和CrisisModule中一样，它还从hero-routing.module.ts中导入了HeroRoutingModule。

The CrisisModule is much the same.

CrisisModule和本模块非常像，我们不再赘述。

试试在线例子。

{@a shared-module}

Shared modules

共享模块

The app is shaping up. But it carries three different versions of the HighlightDirective. And the many files cluttering the app folder level could be better organized.

本应用在继续演进中。让我们感到不爽的是：这里有HighlightDirective的三个不同版本。还有一大堆其它乱七八糟的东西堆在 app 目录这一级，我们得把它们清出去。

Add a SharedModule to hold the common components, directives, and pipes and share them with the modules that need them.

我们添加SharedModule来存放这些公共组件、指令和管道，并且共享给那些需要它们的模块。

Create an src/app/shared folder.

创建src/app/shared目录

Move the AwesomePipe and HighlightDirective from src/app/contact to src/app/shared.

把AwesomePipe和HighlightDirective从src/app/contact移到src/app/shared中。

Delete the HighlightDirective classes from src/app/ and src/app/hero.

从src/app/和src/app/hero目录中删除HighlightDirective类

Create a SharedModule class to own the shared material.

创建SharedModule类来管理这些共享的素材

Update other feature modules to import SharedModule.

更新其它特性模块，导入SharedModule

Here is the SharedModule:

下面就是这个SharedModule：

Note the following:

值得注意的有：

It imports the CommonModule because its component needs common directives.

它导入了CommonModule，这是因为它的组件需要这些公共指令。
It declares and exports the utility pipe, directive, and component classes as expected.

正如我们所期待的，它声明并导出了工具性的管道、指令和组件类。
It re-exports the CommonModule and FormsModule

它重新导出了CommonModule和FormsModule

Re-exporting other modules

重新导出其它模块

If you review the application, you may notice that many components requiring SharedModule directives also use NgIf and NgFor from CommonModule and bind to component properties with [(ngModel)], a directive in the FormsModule. Modules that declare these components would have to import CommonModule, FormsModule, and SharedModule.

当回顾应用程序时，我们注意到很多需要SharedModule的组件也同时用到了来自CommonModule的NgIf和NgFor指令，并且还通过来自FormsModule的[(ngModel)]指令绑定到了组件的属性。那些声明这些组件的模块将不得不同时导入CommonModule、FormsModule和SharedModule。

You can reduce the repetition by having SharedModule re-export CommonModule and FormsModule so that importers of SharedModule get CommonModule and FormsModule for free.

通过让SharedModule重新导出CommonModule和FormsModule模块，我们可以消除这种重复。于是导入SharedModule的模块也同时免费获得了CommonModule和FormsModule。

As it happens, the components declared by SharedModule itself don't bind with [(ngModel)]. Technically, there is no need for SharedModule to import FormsModule.

实际上，SharedModule本身所声明的组件没绑定过[(ngModel)]，那么，严格来说SharedModule并不需要导入FormsModule。

SharedModule can still export FormsModule without listing it among its imports.

这时SharedModule仍然可以导出FormsModule，而不需要先把它列在imports中。

Why TitleComponent isn't shared

为什么 TitleComponent 没有被共享

SharedModule exists to make commonly used components, directives, and pipes available for use in the templates of components in many other modules.

设计SharedModule的目的在于让常用的组件、指令和管道可以被用在很多其它模块的组件模板中。

The TitleComponent is used only once by the AppComponent. There's no point in sharing it.

而TitleComponent只被AppComponent用了一次，因此没必要共享它。

{@a no-shared-module-providers}

Why UserService isn't shared

为什么 UserService 没有被共享

While many components share the same service instances, they rely on Angular dependency injection to do this kind of sharing, not the module system.

虽然很多组件都共享着同一个服务实例，但它们是靠 Angular 的依赖注入体系实现的，而不是模块体系。

Several components of the sample inject the UserService. There should be only one instance of the UserService in the entire application and only one provider of it.

例子中的很多组件都注入了UserService。在整个应用程序中，只应该有一个UserService的实例，并且它只应该有一个提供商。

UserService is an application-wide singleton. You don't want each module to have its own separate instance. Yet there is a real danger of that happening

if the SharedModule provides the UserService.

UserService是全应用级单例。我们不希望每个模块都各自有它的实例。而如果由SharedModule提供UserService，就会导致铁板钉钉的危险。

Do not specify app-wide singleton providers in a shared module. A lazy-loaded module that imports that shared module makes its own copy of the service.

不要在共享模块中把应用级单例添加到providers中。否则如果一个惰性加载模块导入了此共享模块，就会导致它自己也生成一份此服务的实例。

{@a core-module}

The Core module

核心 (Core) 模块

At the moment, the root folder is cluttered with the UserService and TitleComponent that only appear in the root AppComponent. You didn't include them in the SharedModule for reasons just explained.

现在，我们的根目录下只剩下UserService和TitleComponent这两个被根组件AppComponent用到的类没有清理了。但正如我们已经解释过的，它们无法被包含在SharedModule中。

Instead, gather them in a single CoreModule that you import once when the app starts and never import anywhere else.

不过，我们可以把它们收集到单独的CoreModule中，并且只在应用启动时导入它一次，而不会在其它地方导入它。

Perform the following steps:

执行下列步骤：

Create an src/app/core folder.

创建src/app/core文件夹

Move the UserService and TitleComponent from src/app/ to src/app/core.

把UserService和TitleComponent从src/app移到src/app/core中

Create a CoreModule class to own the core material.

创建CoreModule类来管理这些核心素材

Update the AppRoot module to import CoreModule.

修改AppRoot模块，使其导入CoreModule模块

Most of this work is familiar. The interesting part is the CoreModule.

这些都是一些熟悉的普通任务。令人感兴趣的是CoreModule：

You're importing some extra symbols from the Angular core library that you're not using yet. They'll become relevant later in this page.

我们正在从 Angular 核心库中导入一些从未用到的符号，稍后我们会接触它们。

The @NgModule metadata should be familiar. You declare the TitleComponent because this module owns it and you export it because AppComponent (which is in AppModule) displays the title in its template. TitleComponent needs the Angular NgIf directive that you import from CommonModule.

我们对@NgModule的元数据应该很熟悉。由于该模块_拥有_TitleComponent，所以我们声明了它。由于AppComponent（位于AppModule模块）在模板中显示了这个标题，所以我们导出了它。由于TitleComponent需要用到 Angular 的NgIf指令，所以我们导入了CommonModule。

CoreModule provides the UserService. Angular registers that provider with the app root injector, making a singleton instance of the UserService available to any component that needs it, whether that component is eagerly or lazily loaded.

CoreModule_提供_了UserService。Angular 在该应用的根注入器中注册了它的提供商，导致这份UserService的实例在每个需要它的组件中都是可用的，无论那个组件时主动加载的还是惰性加载的。

Why bother?

没必要？

This scenario is clearly contrived. The app is too small to worry about a single service file and a tiny, one-time component.

这个场景设计的是有点生硬。该应用太小了，所以其实并不需要拆分出单独的服务文件和小型的、一次性的组件。

A TitleComponent sitting in the root folder isn't bothering anyone. The root AppModule can register the UserService itself, as it does currently, even if you decide to relocate the UserService file to the src/app/core folder.

把TitleComponent放在根目录中其实也无所谓。即使我们决定把UserService文件挪到app/core目录中，根AppModule也仍然可以自己注册UserService（就像现在这样）。

Real-world apps have more to worry about. They can have several single-use components (such as spinners, message toasts, and modal dialogs) that appear only in the AppComponent template. You don't import them elsewhere so they're not shared in that sense. Yet they're too big and messy to leave loose in the root folder.

但真实的应用要考虑很多。它们有一些只用于AppComponent的模板的一次性的组件（例如：加载动画、消息浮层和模态对话框等）。我们不用在其它地方导入它们，因此没必要共享它们。然而如果把它们留在根目录，还是显得太大、太乱了。

Apps often have many singleton services like this sample's UserService. Each must be registered exactly once, in the app root injector, when the application starts.

应用通常还有很多像这里的UserService这样的单例服务。当程序启动时，每个服务都只能在应用的“根注入器”中注册一次。

While many components inject such services in their constructors—and therefore require JavaScript import statements to import their symbols—no other component or module should define or re-create the services themselves. Their providers aren't shared.

当很多组件在它们的构造函数中注入这些服务时 — 因此也需要用 JavaScript 的import语句来导入它们的符号 — 任何组件或模块自身都不应该定义或重新创建这些服务。因为它们的提供商不是共享的。

We recommend collecting such single-use classes and hiding their details inside a CoreModule. A simplified root AppModule imports CoreModule in its capacity as orchestrator of the application as a whole.

因此我们建议把这些一次性的类收集到CoreModule中，并且隐藏它们的实现细节。简化之后的根模块AppModule导入CoreModule来获取其能力。记住，根模块是整个应用的总指挥，不应该插手过多细节。

Cleanup

清理

Having refactored to a CoreModule and a SharedModule, it's time to clean up the other modules.

我们已经重构完CoreModule和SharedModule，现在开始清理其它模块。

A trimmer AppModule

清理 AppModule

Here is the updated AppModule paired with version 3 for comparison:

这里是更新后的AppModule与其第三版本的对比：

AppModule now has the following qualities:

AppModule现在变得：

A little smaller because many src/app/root classes have moved to other modules.

更小了。因为很多src/app/root下的类被移到了其它模块。
Stable because you'll add future components and providers to other modules, not this one.

更稳定了。因为我们以后会在其它模块中添加组件和服务提供商，而不是这里。
Delegated to imported modules rather than doing work.

导入其它模块并把任务委托给它们，而不是亲力亲为。
Focused on its main task, orchestrating the app as a whole.

聚焦于自己的主要任务：总指挥整个应用程序。

A trimmer ContactModule

清理ContactModule

Here is the new ContactModule paired with the prior version:

这里是新的ContactModule与以前版本的对比：

Notice the following:

注意：

The AwesomePipe and HighlightDirective are gone.

AwesomePipe和HighlightDirective不见了。
The imports include SharedModule instead of CommonModule and FormsModule.

导入SharedModule，不再导入CommonModule和FormsModule。
The new version is leaner and cleaner.

这个新版本更加精简和干净了。

{@a core-for-root}

Configure core services with CoreModule.forRoot

用 CoreModule.forRoot 配置核心服务

A module that adds providers to the application can offer a facility for configuring those providers as well.

为应用添加服务提供商的模块也可以同时提供配置那些提供商的功能。

By convention, the forRoot static method both provides and configures services at the same time. It takes a service configuration object and returns a ModuleWithProviders, which is a simple object with the following properties:

按照约定，模块的静态方法forRoot可以同时提供并配置服务。它接收一个服务配置对象，并返回一个ModuleWithProviders。这个简单对象具有两个属性：

ngModule: the CoreModule class

ngModule - CoreModule类
providers: the configured providers

providers - 配置好的服务提供商

The root AppModule imports the CoreModule and adds the providers to the AppModule providers.

根模块AppModule会导入CoreModule类并把它的providers添加到AppModule的服务提供商中。

More precisely, Angular accumulates all imported providers before appending the items listed in @NgModule.providers. This sequence ensures that whatever you add explicitly to the AppModule providers takes precedence over the providers of imported modules.

更精确的说法是，Angular 会先累加所有导入的提供商，然后才把它们追加到@NgModule.providers中。这样可以确保我们显式添加到AppModule中的那些提供商总是优先于从其它模块中导入的提供商。

Add a CoreModule.forRoot method that configures the core UserService.

现在添加CoreModule.forRoot方法，以便配置核心中的UserService。

You've extended the core UserService with an optional, injected UserServiceConfig. If a UserServiceConfig exists, the UserService sets the user name from that config.

我们曾经用一个可选的、被注入的UserServiceConfig服务扩展过核心的UserService服务。如果有UserServiceConfig，UserService就会据此设置用户名。

Here's CoreModule.forRoot that takes a UserServiceConfig object:

这里的CoreModule.forRoot接收UserServiceConfig对象：

Lastly, call it within the imports list of the AppModule.

最后，我们在AppModule的imports列表中调用它。

The app displays "Miss Marple" as the user instead of the default "Sherlock Holmes".

该应用不再显示默认的 “Sherlock Holmes”，而是用 “Miss Marple” 作为用户名称。

Call forRoot only in the root application module, AppModule. Calling it in any other module, particularly in a lazy-loaded module, is contrary to the intent and can produce a runtime error.

只在应用的根模块AppModule中调用forRoot。如果在其它模块（特别是惰性加载模块）中调用它则违反了设计意图，并会导致运行时错误。

Remember to import the result; don't add it to any other @NgModule list.

别忘了_导入_其返回结果，而且不要把它添加到@NgModule的其它任何列表中。

{@a prevent-reimport}

Prevent reimport of the CoreModule

禁止多次导入CoreModule

Only the root AppModule should import the CoreModule. Bad things happen if a lazy-loaded module imports it.

只有根模块AppModule才能导入CoreModule。如果惰性加载模块导入了它，就会出问题。

You could hope that no developer makes that mistake. Or you can guard against it and fail fast by adding the following CoreModule constructor.

我们可以祈祷任何开发人员都不会犯错。但是最好还是对它进行一些保护，以便让它“尽快出错”。只要把下列代码添加到CoreModule的构造函数中就可以了。

The constructor tells Angular to inject the CoreModule into itself. That seems dangerously circular.

这个构造函数会要求 Angular 把CoreModule注入自身。这看起来像一个危险的循环注入。

The injection would be circular if Angular looked for CoreModule in the current injector. The @SkipSelf decorator means "look for CoreModule in an ancestor injector, above me in the injector hierarchy."

确实，如果 Angular 在当前注入器中查阅CoreModule，这确实会是一个循环引用。不过，@SkipSelf装饰器意味着“在当前注入器的所有祖先注入器中寻找CoreModule。”

If the constructor executes as intended in the AppModule, there is no ancestor injector that could provide an instance of CoreModule. The injector should give up.

如果该构造函数在我们所期望的AppModule中运行，就没有任何祖先注入器能够提供CoreModule的实例，于是注入器会放弃查找。

By default, the injector throws an error when it can't find a requested provider. The @Optional decorator means not finding the service is OK. The injector returns null, the parentModule parameter is null, and the constructor concludes uneventfully.

默认情况下，当注入器找不到想找的提供商时，会抛出一个错误。但@Optional装饰器表示找不到该服务也无所谓。于是注入器会返回null，parentModule参数也就被赋成了空值，而构造函数没有任何异常。

It's a different story if you improperly import CoreModule into a lazy-loaded module such as HeroModule (try it).

如果我们错误的把CoreModule导入了一个惰性加载模块（例如HeroModule）中，那就不一样了。

Angular creates a lazy-loaded module with its own injector, a child of the root injector. @SkipSelf causes Angular to look for a CoreModule in the parent injector, which this time is the root injector. Of course it finds the instance imported by the root AppModule. Now parentModule exists and the constructor throws the error.

Angular 创建一个惰性加载模块，它具有自己的注入器，它是根注入器的子注入器。 @SkipSelf让 Angular 在其父注入器中查找CoreModule，这次，它的父注入器却是根注入器了（而上次父注入器是空）。当然，这次它找到了由根模块AppModule导入的实例。该构造函数检测到存在parentModule，于是抛出一个错误。

Conclusion

总结

You made it! You can examine and download the complete source for this final version from the live example.

完工！你可以到下面的在线例子中试验它，并下载最终版本的全部源码。

Frequently asked questions

常见问题 (FAQ)

Now that you understand NgModules, you may be interested in the companion NgModule FAQs page with its ready answers to specific design and implementation questions.

现在，你已经理解了 Angular 的模块。可能你还会对烹饪宝典中的 Angular 模块常见问题感兴趣，它解答了很多关于设计和实现方面的问题。

86 KiB Raw Blame History Unescape Escape