honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

把立即加载统一改为主动加载

Browse Source
This commit is contained in:
Zhicheng Wang 2016-10-12 15:23:34 +08:00
parent 72b0ec623e
commit 7aa3c2320a
3 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
public/docs/ts/latest/cookbook/ngmodule-faq.jade
View File

@ -681,7 +681,7 @@ a#q-component-scoped-providers
If you must load the module eagerly, when the application starts, If you must load the module eagerly, when the application starts,
***provide the service in a component instead.*** ***provide the service in a component instead.***
如果你必须在应用程序启动时立即加载该模块，***就改成在组件中提供该服务***。 如果你必须在应用程序启动时主动加载该模块，***就改成在组件中提供该服务***。
Continuing with the same example, suppose the components of a module truly require a private, custom `HttpBackend`. Continuing with the same example, suppose the components of a module truly require a private, custom `HttpBackend`.
@ -845,7 +845,7 @@ a#q-why-bad
When the app starts, Angular eagerly loads the `AppModule` and the `ContactModule`. When the app starts, Angular eagerly loads the `AppModule` and the `ContactModule`.
当应用启动时，Angular立即加载了`AppModule`和`ContactModule`。 当应用启动时，Angular主动加载了`AppModule`和`ContactModule`。
Both instances of the imported `SharedModule` would provide the `UserService`. Both instances of the imported `SharedModule` would provide the `UserService`.
Angular registers one of them in the root app injector (see [above](#q-reimport)). Angular registers one of them in the root app injector (see [above](#q-reimport)).
@ -873,7 +873,7 @@ a#q-why-bad
当Angular创建一个惰性加载的`HeroComponent`时，它必须注入一个`UserService`。 当Angular创建一个惰性加载的`HeroComponent`时，它必须注入一个`UserService`。
这次，它会从惰性加载模块的*子注入器*中查找`UserService`的提供商，并用它创建一个`UserService`的新实例。 这次，它会从惰性加载模块的*子注入器*中查找`UserService`的提供商，并用它创建一个`UserService`的新实例。
这个`UserService`实例与Angular在立即加载的组件中注入的那个全应用级单例对象截然不同。 这个`UserService`实例与Angular在主动加载的组件中注入的那个全应用级单例对象截然不同。
That's almost certainly a mistake. That's almost certainly a mistake.
@ -915,7 +915,7 @@ a#q-why-child-injector
Why doesn't Angular add lazy loaded providers to the app root injector as it does for eagerly loaded modules? Why doesn't Angular add lazy loaded providers to the app root injector as it does for eagerly loaded modules?
Why the inconsistency? Why the inconsistency?
为什么Angular不能像立即加载模块那样把惰性加载模块的提供商也添加到应用程序的根注入器中呢？为什么会出现这种不一致？ 为什么Angular不能像主动加载模块那样把惰性加载模块的提供商也添加到应用程序的根注入器中呢？为什么会出现这种不一致？
The answer is grounded in a fundamental characteristic of the Angular dependency injection system. The answer is grounded in a fundamental characteristic of the Angular dependency injection system.
An injector can add providers _until it is first used_. An injector can add providers _until it is first used_.
@ -929,7 +929,7 @@ a#q-why-child-injector
_before_ creating its first component and injecting any of the provided services. _before_ creating its first component and injecting any of the provided services.
Once the application begins, the app root injector is closed to new providers. Once the application begins, the app root injector is closed to new providers.
当应用启动时，Angular会首先使用所有立即加载模块中的提供商来配置根注入器，这发生在它创建第一个组件以及注入任何服务之前。 当应用启动时，Angular会首先使用所有主动加载模块中的提供商来配置根注入器，这发生在它创建第一个组件以及注入任何服务之前。
一旦应用开始工作，应用的根注入器就不再接受新的提供商了。 一旦应用开始工作，应用的根注入器就不再接受新的提供商了。
Time passes. Application logic triggers lazy loading of a module. Time passes. Application logic triggers lazy loading of a module.
@ -1206,7 +1206,7 @@ a#q-module-recommendations
Import the `SharedModule` in your _feature_ modules, Import the `SharedModule` in your _feature_ modules,
both those loaded when the app starts and those you lazy load later. both those loaded when the app starts and those you lazy load later.
在任何特性模块中（无论是你在应用启动时立即加载的模块还是之后惰性加载的模块），你都可以随意导入这个`SharedModule`。 在任何特性模块中（无论是你在应用启动时主动加载的模块还是之后惰性加载的模块），你都可以随意导入这个`SharedModule`。
#### _CoreModule_ #### _CoreModule_
Create a `CoreModule` with `providers` for the singleton services you load when the application starts. Create a `CoreModule` with `providers` for the singleton services you load when the application starts.
@ -1350,15 +1350,15 @@ table
`HeroModule` and `CrisisModule` are lazy loaded. They aren't mentioned among the `AppModule` imports. `HeroModule` and `CrisisModule` are lazy loaded. They aren't mentioned among the `AppModule` imports.
惰性加载的路由特性模块也不应该被任何模块*导出*。 惰性加载的路由特性模块也不应该被任何模块*导出*。
那么做会触发一次立即加载，破坏了我们惰性加载的目的。 那么做会触发一次主动加载，破坏了我们惰性加载的目的。
`HeroModule`和`CrisisModule`是惰性加载的。它们没有出现在`AppModule`的`imports`中。 `HeroModule`和`CrisisModule`是惰性加载的。它们没有出现在`AppModule`的`imports`中。
But an eager loaded Routed Feature Module must be imported by another module But an eager loaded Routed Feature Module must be imported by another module
so that the compiler learns about its components. so that the compiler learns about its components.
`ContactModule` is eager loaded and, therefore, is listed among the `AppModule` imports. `ContactModule` is eager loaded and, therefore, is listed among the `AppModule` imports.
而立即加载的路由特性模块必须被其它模块导入，以便编译器了解它有哪些组件。 而主动加载的路由特性模块必须被其它模块导入，以便编译器了解它有哪些组件。
`ContactModule`就是立即加载的，因此它也被列在了`AppModule`的`imports`中。 `ContactModule`就是主动加载的，因此它也被列在了`AppModule`的`imports`中。
Routed Feature Modules rarely have _providers_ for reasons [explained earlier](#q-why-bad). Routed Feature Modules rarely have _providers_ for reasons [explained earlier](#q-why-bad).
When they do, the lifetime of the provided services When they do, the lifetime of the provided services

10
public/docs/ts/latest/guide/ngmodule.jade
View File

@ -26,7 +26,7 @@ block includes
This page explains how to **create** `NgModule` classes and how to load them, This page explains how to **create** `NgModule` classes and how to load them,
either immediately when the application launches or later, as needed, via the [Router](router.html). either immediately when the application launches or later, as needed, via the [Router](router.html).
本章将会讲解如何**创建**`NgModule`类，以及如何加载它们 —— 可以在程序启动时立即加载，也可以稍后由[路由器](router.html)按需加载。 本章将会讲解如何**创建**`NgModule`类，以及如何加载它们 —— 可以在程序启动时主动加载，也可以稍后由[路由器](router.html)按需加载。
## Table of Contents ## Table of Contents
@ -132,7 +132,7 @@ a#angular-modularity
Modules can be loaded eagerly when the application starts. Modules can be loaded eagerly when the application starts.
They can also be _lazy loaded_ asynchronously by the router. They can also be _lazy loaded_ asynchronously by the router.
模块可能在应用启动时立即加载，也可能由路由器进行异步_惰性加载_。 模块可能在应用启动时主动加载，也可能由路由器进行异步_惰性加载_。
An Angular module is a class decorated with `@NgModule` metadata. The metadata: An Angular module is a class decorated with `@NgModule` metadata. The metadata:
@ -1157,7 +1157,7 @@ a#lazy-load
* The `ContactModule` continues to be "eagerly" loaded when the application starts. * The `ContactModule` continues to be "eagerly" loaded when the application starts.
* `ContactModule`仍然会在应用启动时被立即加载。 * `ContactModule`仍然会在应用启动时被主动加载。
* `HeroModule` and the `CrisisModule` are lazy loaded. * `HeroModule` and the `CrisisModule` are lazy loaded.
@ -1363,7 +1363,7 @@ a#hero-module
The lazy loaded `HeroModule` and `CrisisModule` follow the same principles as any feature 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`. They don't look different from the eagerly loaded `ContactModule`.
惰性加载的`HeroModule`和`CrisisModule`与其它特性模块遵循同样的规则。它们和“立即加载”的`ContactModule`看上去没有任何区别。 惰性加载的`HeroModule`和`CrisisModule`与其它特性模块遵循同样的规则。它们和“主动加载”的`ContactModule`看上去没有任何区别。
The `HeroModule` is a bit more complex than the `CrisisModule` which makes it The `HeroModule` is a bit more complex than the `CrisisModule` which makes it
a more interesting and useful example. Here's its file structure: a more interesting and useful example. Here's its file structure:
@ -1602,7 +1602,7 @@ a#core-module
making a singleton instance of the `UserService` available to any component that needs it, making a singleton instance of the `UserService` available to any component that needs it,
whether that component is eagerly or lazily loaded. whether that component is eagerly or lazily loaded.
`CoreModule`*提供*了`UserService`。Angular在该应用的“根注入器”中注册了它的提供商，导致这份`UserService`的实例在每个需要它的组件中都是可用的，无论那个组件时立即加载的还是惰性加载的。 `CoreModule`*提供*了`UserService`。Angular在该应用的“根注入器”中注册了它的提供商，导致这份`UserService`的实例在每个需要它的组件中都是可用的，无论那个组件时主动加载的还是惰性加载的。
.l-sub-section .l-sub-section
:marked :marked

6
public/docs/ts/latest/guide/style-guide.jade
View File

@ -2020,7 +2020,7 @@ a(href="#toc") 回到顶部
:marked :marked
**Why?** `CoreModule` provides one or more singleton services. Angular registers the providers with the app root injector, making a singleton instance of each service available to any component that needs them, whether that component is eagerly or lazily loaded. **Why?** `CoreModule` provides one or more singleton services. Angular registers the providers with the app root injector, making a singleton instance of each service available to any component that needs them, whether that component is eagerly or lazily loaded.
**为何？** `CoreModule`提供了一个或多个单例服务。Angular使用应用的根注入器注册这些服务提供商，让每个服务的这个单例对象对所有需要它们的组件都是可用的，而不用管该组件是通过立即加载还是惰性加载的方式加载的。 **为何？** `CoreModule`提供了一个或多个单例服务。Angular使用应用的根注入器注册这些服务提供商，让每个服务的这个单例对象对所有需要它们的组件都是可用的，而不用管该组件是通过主动加载还是惰性加载的方式加载的。
.s-why .s-why
:marked :marked
@ -2061,7 +2061,7 @@ a(href="#toc") 回到顶部
:marked :marked
**Why?** An eagerly loaded feature module already has access to the `AppModule`'s injector, and thus the `CoreModule`'s services. **Why?** An eagerly loaded feature module already has access to the `AppModule`'s injector, and thus the `CoreModule`'s services.
**为何？**立即加载的特性模块已经准备好了访问`AppModule`的注入器，因此也能取得`CoreModule`中的服务。 **为何？**主动加载的特性模块已经准备好了访问`AppModule`的注入器，因此也能取得`CoreModule`中的服务。
.s-rule.do .s-rule.do
:marked :marked
@ -2289,7 +2289,7 @@ a(href="#toc") 回到顶部
:marked :marked
**Why?** Directly importing and using a module will load it immediately when the intention is to load it on demand. **Why?** Directly importing and using a module will load it immediately when the intention is to load it on demand.
**为何？**直接导入并使用此模块会立即加载它，而我们原本的设计意图是按需加载它。 **为何？**直接导入并使用此模块会主动加载它，而我们原本的设计意图是按需加载它。
a(href="#toc") Back to top a(href="#toc") Back to top