风格指南

Style Guide

如果你正在寻找关于 Angular 语法、约定和应用组织结构的官方指南，那你就来对了。本风格指南介绍了提倡的约定，更重要的是，解释了为什么。

Looking for an opinionated guide to Angular syntax, conventions, and application structure? Step right in! This style guide presents preferred conventions and, as importantly, explains why.

风格指南的用词

Style vocabulary

每个指导原则都会描述好的或者坏的做法，所有指导原则都用同样的风格描述。

Each guideline describes either a good or bad practice, and all have a consistent presentation.

指导原则中使用的词汇用来表明推荐的程度。

The wording of each guideline indicates how strong the recommendation is.

坚持意味着总是应该遵循的约定。说"总是"可能显得有点绝对，应该"总是"遵循的指导原则非常少，不过，只有遇到极不寻常的情况才能打破坚持的原则。

Do is one that should always be followed. Always might be a bit too strong of a word. Guidelines that literally should always be followed are extremely rare. On the other hand, you need a really unusual case for breaking a Do guideline.

考虑表示通常应该遵循的指导原则。如果你能完全理解指导原则背后的含义，并且有很好的理由违反它，那就改吧。但是请保持一致。

Consider guidelines should generally be followed. If you fully understand the meaning behind the guideline and have a good reason to deviate, then do so. Please strive to be consistent.

避免表示你绝对不应该做的事。需要避免的代码范例会有明显的红色标题。

Avoid indicates something you should almost never do. Code examples to avoid have an unmistakable red header.

为何？会给出随后的建议的理由。

Why? gives reasons for following the previous recommendations.

文件结构约定

File structure conventions

在一些代码例子中，有的文件有一个或多个相似名字的配套文件。（例如 hero.component.ts 和 hero.component.html）。

Some code examples display a file that has one or more similarly named companion files. For example, hero.component.ts and hero.component.html.

本指南将会使用像 hero.component.ts|html|css|spec 的简写来表示上面描述的多个文件，目的是保持本指南的简洁性，增加描述文件结构时的可读性。

The guideline uses the shortcut hero.component.ts|html|css|spec to represent those various files. Using this shortcut makes this guide's file structures easier to read and more terse.

单一职责

Single responsibility

对所有的组件、服务等等应用单一职责原则 (SRP)。这样可以让应用更干净、更易读、更易维护、更易测试。

Apply the single responsibility principle (SRP) to all components, services, and other symbols. This helps make the app cleaner, easier to read and maintain, and more testable.

单一规则

Rule of One

风格 01-01

Style 01-01

坚持每个文件只定义一样东西（例如服务或组件）。

Do define one thing, such as a service or component, per file.

考虑把文件大小限制在 400 行代码以内。

Consider limiting files to 400 lines of code.

为何？单组件文件非常容易阅读、维护，并能防止在版本控制系统里与团队冲突。

Why? One component per file makes it far easier to read, maintain, and avoid collisions with teams in source control.

为何？单组件文件可以防止一些隐蔽的程序缺陷，当把多个组件合写在同一个文件中时，可能造成共享变量、创建意外的闭包，或者与依赖之间产生意外耦合等情况。

Why? One component per file avoids hidden bugs that often arise when combining components in a file where they may share variables, create unwanted closures, or unwanted coupling with dependencies.

为何？单独的组件通常是该文件默认的导出，可以用路由器实现按需加载。

Why? A single component can be the default export for its file which facilitates lazy loading with the router.

最关键的是，可以让代码更加可复用、更容易阅读，减少出错的可能性。

The key is to make the code more reusable, easier to read, and less mistake prone.

下面的负面例子定义了 AppComponent，它来引导应用程序，定义了 Hero 模型对象，并从服务器加载了英雄 ... 所有都在同一个文件。 不要这么做。

The following negative example defines the AppComponent, bootstraps the app, defines the Hero model object, and loads heroes from the server all in the same file. Don't do this.

app/heroes/hero.component.ts

      
      /* avoid */
import { Component, NgModule, OnInit } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
 
class Hero {
  id: number;
  name: string;
}
 
@Component({
  selector: 'my-app',
  template: `
      <h1>{{title}}</h1>
      <pre>{{heroes | json}}</pre>
    `,
  styleUrls: ['app/app.component.css']
})
class AppComponent implements OnInit {
  title = 'Tour of Heroes';
 
  heroes: Hero[] = [];
 
  ngOnInit() {
    getHeroes().then(heroes => (this.heroes = heroes));
  }
}
 
@NgModule({
  imports: [BrowserModule],
  declarations: [AppComponent],
  exports: [AppComponent],
  bootstrap: [AppComponent]
})
export class AppModule {}
 
platformBrowserDynamic().bootstrapModule(AppModule);
 
const HEROES: Hero[] = [
  { id: 1, name: 'Bombasto' },
  { id: 2, name: 'Tornado' },
  { id: 3, name: 'Magneta' }
];
 
function getHeroes(): Promise<Hero[]> {
  return Promise.resolve(HEROES); // TODO: get hero data from the server;
}

最好将组件及其支撑部件重新分配到独立的文件。

It is a better practice to redistribute the component and its supporting classes into their own, dedicated files.

main.ts

app/app.module.ts

app/app.component.ts

app/heroes/heroes.component.ts

app/heroes/shared/hero.service.ts

app/heroes/shared/hero.model.ts

app/heroes/shared/mock-heroes.ts

      
      import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';

import { AppModule } from './app/app.module';

platformBrowserDynamic().bootstrapModule(AppModule);

随着应用程序的成长，本法则会变得越来越重要。

As the app grows, this rule becomes even more important.

回到顶部

小函数

Small functions

风格 01-02

Style 01-02

坚持定义简单函数

Do define small functions

考虑限制在 75 行之内。

Consider limiting to no more than 75 lines.

为何？简单函数更易于测试，特别是当它们只做一件事，只为一个目的服务时。

Why? Small functions are easier to test, especially when they do one thing and serve one purpose.

为何？简单函数促进代码重用。

Why? Small functions promote reuse.

为何？简单函数更易于阅读。

Why? Small functions are easier to read.

为何？简单函数更易于维护。

Why? Small functions are easier to maintain.

为何？小函数可避免易在大函数中产生的隐蔽性错误，例如与外界共享变量、创建意外的闭包或与依赖之间产生意外耦合等。

Why? Small functions help avoid hidden bugs that come with large functions that share variables with external scope, create unwanted closures, or unwanted coupling with dependencies.

回到顶部

命名

Naming

命名约定对可维护性和可读性非常重要。本指南为文件名和符号名推荐了一套命名约定。

Naming conventions are hugely important to maintainability and readability. This guide recommends naming conventions for the file name and the symbol name.

总体命名原则

General Naming Guidelines

风格 02-01

Style 02-01

坚持所有符号使用一致的命名规则。

Do use consistent names for all symbols.

坚持遵循同一个模式来描述符号的特性和类型。推荐的模式为 feature.type.ts。

Do follow a pattern that describes the symbol's feature then its type. The recommended pattern is feature.type.ts.

为何？命名约定提供了一致的方式来查找内容，让你一眼就能找到。项目的一致性是至关重要的。团队内的一致性也很重要。整个公司的一致性会提供惊人的效率。

Why? Naming conventions help provide a consistent way to find content at a glance. Consistency within the project is vital. Consistency with a team is important. Consistency across a company provides tremendous efficiency.

为何？命名约定帮助你更快得找到想找的代码，也更容易理解它。

Why? The naming conventions should simply help find desired code faster and make it easier to understand.

为何？目录名和文件名应该清楚的传递它们的意图。例如，app/heroes/hero-list.component.ts 包含了一个用来管理英雄列表的组件。

Why? Names of folders and files should clearly convey their intent. For example, app/heroes/hero-list.component.ts may contain a component that manages a list of heroes.

回到顶部

使用点和横杠来分隔文件名

Separate file names with dots and dashes

风格 02-02

Style 02-02

坚持在描述性名字中，用横杠来分隔单词。

Do use dashes to separate words in the descriptive name.

坚持使用点来分隔描述性名字和类型。

Do use dots to separate the descriptive name from the type.

坚持遵循先描述组件特性，再描述它的类型的模式，对所有组件使用一致的类型命名规则。推荐的模式为 feature.type.ts。

Do use consistent type names for all components following a pattern that describes the component's feature then its type. A recommended pattern is feature.type.ts.

坚持使用惯用的后缀来描述类型，包括 *.service、*.component、*.pipe、.module、.directive。必要时可以创建更多类型名，但必须注意，不要创建太多。

Do use conventional type names including .service, .component, .pipe, .module, and .directive. Invent additional type names if you must but take care not to create too many.

为何？类型名字提供一致的方式来快速的识别文件中有什么。

Why? Type names provide a consistent way to quickly identify what is in the file.

为何？ 类型名可以让你轻松利用编辑器或者 IDE 的模糊搜索功能找到特定文件类型。

Why? Type names make it easy to find a specific file type using an editor or IDE's fuzzy search techniques.

为何？ 像 .service 这样的没有简写过的类型名字，描述清楚，毫不含糊。像 .srv, .svc, 和 .serv 这样的简写可能令人困惑。

Why? Unabbreviated type names such as .service are descriptive and unambiguous. Abbreviations such as .srv, .svc, and .serv can be confusing.

为何？为自动化任务提供模式匹配。

Why? Type names provide pattern matching for any automated tasks.

回到顶部

符号名与文件名

Symbols and file names

风格 02-03

Style 02-03

坚持为所有东西使用一致的命名约定，以它们所代表的东西命名。

Do use consistent names for all assets named after what they represent.

坚持使用大写驼峰命名法来命名类。符号名匹配它所在的文件名。

Do use upper camel case for class names.

坚持在符号名后面追加约定的类型后缀（例如 Component、Directive、Module、Pipe、Service）。

Do match the name of the symbol to the name of the file.

坚持在符号名后面追加约定的类型后缀（例如 .component.ts、.directive.ts、.module.ts、.pipe.ts、.service.ts）。

Do append the symbol name with the conventional suffix (such as Component, Directive, Module, Pipe, or Service) for a thing of that type.

坚持在文件名后面追加约定的类型后缀（例如 .component.ts、.directive.ts、.module.ts、.pipe.ts、.service.ts）。

Do give the filename the conventional suffix (such as .component.ts, .directive.ts, .module.ts, .pipe.ts, or .service.ts) for a file of that type.

为何？遵循一致的约定可以快速识别和引用不同类型的资产。

Why? Consistent conventions make it easy to quickly identify and reference assets of different types.

符号名 Symbol Name	文件名 File Name
@Component({ ... }) export class AppComponent { } `@Component({ ... }) export class AppComponent { }`	app.component.ts
@Component({ ... }) export class HeroesComponent { } `@Component({ ... }) export class HeroesComponent { }`	heroes.component.ts
@Component({ ... }) export class HeroListComponent { } `@Component({ ... }) export class HeroListComponent { }`	hero-list.component.ts
@Component({ ... }) export class HeroDetailComponent { } `@Component({ ... }) export class HeroDetailComponent { }`	hero-detail.component.ts
@Directive({ ... }) export class ValidationDirective { } `@Directive({ ... }) export class ValidationDirective { }`	validation.directive.ts
@NgModule({ ... }) export class AppModule `@NgModule({ ... }) export class AppModule`	app.module.ts
@Pipe({ name: 'initCaps' }) export class InitCapsPipe implements PipeTransform { } `@Pipe({ name: 'initCaps' }) export class InitCapsPipe implements PipeTransform { }`	init-caps.pipe.ts
@Injectable() export class UserProfileService { } `@Injectable() export class UserProfileService { }`	user-profile.service.ts

回到顶部

服务名

Service names

风格 02-04

Style 02-04

坚持使用一致的规则命名服务，以它们的特性来命名。

Do use consistent names for all services named after their feature.

坚持为服务的类名加上 Service 后缀。例如，获取数据或英雄列表的服务应该命名为 DataService 或 HeroService。

Do suffix a service class name with Service. For example, something that gets data or heroes should be called a DataService or a HeroService.

有些词汇显然就是服务，比如那些以“-er”后缀结尾的。比如把记日志的服务命名为 Logger 就比 LoggerService 更好些。需要在你的项目中决定这种特例是否可以接受。但无论如何，都要尽量保持一致。

A few terms are unambiguously services. They typically indicate agency by ending in "-er". You may prefer to name a service that logs messages Logger rather than LoggerService. Decide if this exception is agreeable in your project. As always, strive for consistency.

为何？提供一致的方式来快速识别和引用服务。

Why? Provides a consistent way to quickly identify and reference services.

为何？像 Logger 这样的清楚的服务名不需要后缀。

Why? Clear service names such as Logger do not require a suffix.

为何？像 Credit 这样的，服务名是名词，需要一个后缀。当不能明显分辨它是服务还是其它东西时，应该添加后缀。

Why? Service names such as Credit are nouns and require a suffix and should be named with a suffix when it is not obvious if it is a service or something else.

符号名 Symbol Name	文件名 File Name
@Injectable() export class HeroDataService { } `@Injectable() export class HeroDataService { }`	hero-data.service.ts
@Injectable() export class CreditService { } `@Injectable() export class CreditService { }`	credit.service.ts
@Injectable() export class Logger { } `@Injectable() export class Logger { }`	logger.service.ts

符号名

Symbol Name

文件名

File Name

      
      @Injectable()
export class HeroDataService { }

hero-data.service.ts

      
      @Injectable()
export class CreditService { }

credit.service.ts

      
      @Injectable()
export class Logger { }

logger.service.ts

回到顶部

引导

Bootstrapping

风格 02-05

Style 02-05

坚持把应用的引导程序和平台相关的逻辑放到名为 main.ts 的文件里。

Do put bootstrapping and platform logic for the app in a file named main.ts.

坚持在引导逻辑中包含错误处理代码。

Do include error handling in the bootstrapping logic.

避免把应用逻辑放在 main.ts 中，而应放在组件或服务里。

Avoid putting app logic in main.ts. Instead, consider placing it in a component or service.

为何？应用的启动逻辑遵循一致的约定。

Why? Follows a consistent convention for the startup logic of an app.

为何？这是从其它技术平台借鉴的常用约定。

Why? Follows a familiar convention from other technology platforms.

main.ts

      
      import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';

import { AppModule }              from './app/app.module';

platformBrowserDynamic().bootstrapModule(AppModule)
  .then(success => console.log(`Bootstrap success`))
  .catch(err => console.error(err));

回到顶部

组件选择器

Component selectors

风格 05-02

Style 05-02

坚持使用中线命名法（dashed-case）或叫烤串命名法（kebab-case）来命名组件的元素选择器。

Do use dashed-case or kebab-case for naming the element selectors of components.

为何？让元素名和自定义元素规范保持一致。

Why? Keeps the element names consistent with the specification for Custom Elements.

app/heroes/shared/hero-button/hero-button.component.ts

      
      /* avoid */

@Component({
  selector: 'tohHeroButton',
  templateUrl: './hero-button.component.html'
})
export class HeroButtonComponent {}

app/heroes/shared/hero-button/hero-button.component.ts

app/app.component.html

      
      @Component({
  selector: 'toh-hero-button',
  templateUrl: './hero-button.component.html'
})
export class HeroButtonComponent {}

回到顶部

为组件添加自定义前缀

Component custom prefix

风格 02-07

Style 02-07

坚持使用带连字符的小写元素选择器值（例如 admin-users）。

Do use a hyphenated, lowercase element selector value (e.g. admin-users).

坚持为组件选择器添加自定义前缀。例如，toh 前缀表示 Tour of Heroes（英雄指南），而前缀 `admin 表示管理特性区。

Do use a custom prefix for a component selector. For example, the prefix toh represents from Tour of Heroes and the prefix admin represents an admin feature area.

坚持使用前缀来识别特性区或者应用程序本身。

Do use a prefix that identifies the feature area or the app itself.

为何？防止与其它应用中的组件和原生 HTML 元素发生命名冲突。

Why? Prevents element name collisions with components in other apps and with native HTML elements.

为何？更容易在其它应用中推广和共享组件。

Why? Makes it easier to promote and share the component in other apps.

为何？组件在 DOM 中更容易被区分出来。

Why? Components are easy to identify in the DOM.

app/heroes/hero.component.ts

      
      /* avoid */

// HeroComponent is in the Tour of Heroes feature
@Component({
  selector: 'hero'
})
export class HeroComponent {}

app/users/users.component.ts

      
      /* avoid */

// UsersComponent is in an Admin feature
@Component({
  selector: 'users'
})
export class UsersComponent {}

app/heroes/hero.component.ts

      
      @Component({
  selector: 'toh-hero'
})
export class HeroComponent {}

app/users/users.component.ts

      
      @Component({
  selector: 'admin-users'
})
export class UsersComponent {}

回到顶部

指令选择器

Directive selectors

风格 02-06

Style 02-06

坚持使用小驼峰形式命名指令的选择器。

Do Use lower camel case for naming the selectors of directives.

为何？可以让指令中的属性名与视图中绑定的属性名保持一致。

Why? Keeps the names of the properties defined in the directives that are bound to the view consistent with the attribute names.

为何？ Angular 的 HTML 解析器是大小写敏感的，可以识别小驼峰形式。

Why? The Angular HTML parser is case sensitive and recognizes lower camel case.

回到顶部

为指令添加自定义前缀

Directive custom prefix

风格 02-08

Style 02-08

坚持为指令的选择器添加自定义前缀（例如前缀 toh 来自 Tour of Heroes）。

Do use a custom prefix for the selector of directives (e.g, the prefix toh from Tour of Heroes).

坚持用小驼峰形式拼写非元素选择器，除非该选择器用于匹配原生 HTML 属性。

Do spell non-element selectors in lower camel case unless the selector is meant to match a native HTML attribute.

为何？防止名字冲突。

Why? Prevents name collisions.

为何？指令更加容易被识别。

Why? Directives are easily identified.

app/shared/validate.directive.ts

      
      /* avoid */

@Directive({
  selector: '[validate]'
})
export class ValidateDirective {}

app/shared/validate.directive.ts

      
      @Directive({
  selector: '[tohValidate]'
})
export class ValidateDirective {}

回到顶部

管道名

Pipe names

风格 02-09

Style 02-09

坚持为所有管道使用一致的命名约定，用它们的特性来命名。

Do use consistent names for all pipes, named after their feature.

为何？提供一致的方式快速识别和引用管道。

Why? Provides a consistent way to quickly identify and reference pipes.

符号名 Symbol Name	文件名 File Name
@Pipe({ name: 'ellipsis' }) export class EllipsisPipe implements PipeTransform { } `@Pipe({ name: 'ellipsis' }) export class EllipsisPipe implements PipeTransform { }`	ellipsis.pipe.ts
@Pipe({ name: 'initCaps' }) export class InitCapsPipe implements PipeTransform { } `@Pipe({ name: 'initCaps' }) export class InitCapsPipe implements PipeTransform { }`	init-caps.pipe.ts

符号名

Symbol Name

文件名

File Name

      
      @Pipe({ name: 'ellipsis' })
export class EllipsisPipe implements PipeTransform { }

ellipsis.pipe.ts

      
      @Pipe({ name: 'initCaps' })
export class InitCapsPipe implements PipeTransform { }

init-caps.pipe.ts

回到顶部

单元测试文件名

Unit test file names

风格 02-10

Style 02-10

坚持测试规格文件名与被测试组件文件名相同。

Do name test specification files the same as the component they test.

坚持测试规格文件名添加 .spec 后缀。

Do name test specification files with a suffix of .spec.

为何？提供一致的方式来快速识别测试。

Why? Provides a consistent way to quickly identify tests.

为何？提供一个与 karma 或者其它测试运行器相配的命名模式。

Why? Provides pattern matching for karma or other test runners.

测试类型 Test Type	文件名 File Names
组件 Components	heroes.component.spec.ts hero-list.component.spec.ts hero-detail.component.spec.ts
服务 Services	logger.service.spec.ts hero.service.spec.ts filter-text.service.spec.ts
管道 Pipes	ellipsis.pipe.spec.ts init-caps.pipe.spec.ts

测试类型

Test Type

文件名

File Names

组件

Components

heroes.component.spec.ts

hero-list.component.spec.ts

hero-detail.component.spec.ts

服务

Services

logger.service.spec.ts

hero.service.spec.ts

filter-text.service.spec.ts

管道

Pipes

ellipsis.pipe.spec.ts

init-caps.pipe.spec.ts

回到顶部

端到端（E2E）测试的文件名

End-to-End (E2E) test file names

风格 02-11

Style 02-11

坚持端到端测试规格文件和它们所测试的特性同名，添加 .e2e-spec 后缀。

Do name end-to-end test specification files after the feature they test with a suffix of .e2e-spec.

为何？提供一致的方式快速识别端到端测试文件。

Why? Provides a consistent way to quickly identify end-to-end tests.

为何？提供一个与测试运行器和构建自动化匹配的模式。

Why? Provides pattern matching for test runners and build automation.

测试类型 Test Type	文件名 File Names
端到端测试 End-to-End Tests	app.e2e-spec.ts heroes.e2e-spec.ts

测试类型

Test Type

文件名

File Names

端到端测试

End-to-End Tests

app.e2e-spec.ts

heroes.e2e-spec.ts

回到顶部

Angular NgModule 命名

Angular NgModule names

风格 02-12

Style 02-12

坚持为符号名添加 Module 后缀

Do append the symbol name with the suffix Module.

坚持为文件名添加 .module.ts 扩展名。

Do give the file name the .module.ts extension.

坚持用特性名和所在目录命名模块。

Do name the module after the feature and folder it resides in.

为何？提供一致的方式来快速标识和引用模块。

Why? Provides a consistent way to quickly identify and reference modules.

为何？大驼峰命名法是一种命名约定，用来标识可用构造函数实例化的对象。

Why? Upper camel case is conventional for identifying objects that can be instantiated using a constructor.

为何？很容易就能看出这个模块是同名特性的根模块。

Why? Easily identifies the module as the root of the same named feature.

坚持为 RoutingModule 类名添加 RoutingModule 后缀。

Do suffix a RoutingModule class name with RoutingModule.

坚持为 RoutingModule 的文件名添加 -routing.module.ts 后缀。

Do end the filename of a RoutingModule with -routing.module.ts.

为何？RoutingModule 是一种专门用来配置 Angular 路由器的模块。 “类名和文件名保持一致”的约定使这些模块易于发现和验证。

Why? A RoutingModule is a module dedicated exclusively to configuring the Angular router. A consistent class and file name convention make these modules easy to spot and verify.

符号名 Symbol Name	文件名 File Name
@NgModule({ ... }) export class AppModule { } `@NgModule({ ... }) export class AppModule { }`	app.module.ts
@NgModule({ ... }) export class HeroesModule { } `@NgModule({ ... }) export class HeroesModule { }`	heroes.module.ts
@NgModule({ ... }) export class VillainsModule { } `@NgModule({ ... }) export class VillainsModule { }`	villains.module.ts
@NgModule({ ... }) export class AppRoutingModule { } `@NgModule({ ... }) export class AppRoutingModule { }`	app-routing.module.ts
@NgModule({ ... }) export class HeroesRoutingModule { } `@NgModule({ ... }) export class HeroesRoutingModule { }`	heroes-routing.module.ts

回到顶部

编程约定

Coding conventions

坚持一致的编程、命名和空格的约定。

Have a consistent set of coding, naming, and whitespace conventions.

类

Classes

风格 03-01

Style 03-01

坚持使用大写驼峰命名法来命名类。

Do use upper camel case when naming classes.

为何？遵循类命名传统约定。

Why? Follows conventional thinking for class names.

为何？类可以被实例化和构造实例。根据约定，用大写驼峰命名法来标识可构造的东西。

Why? Classes can be instantiated and construct an instance. By convention, upper camel case indicates a constructable asset.

app/shared/exception.service.ts

      
      /* avoid */

export class exceptionService {
  constructor() { }
}

app/shared/exception.service.ts

      
      export class ExceptionService {
  constructor() { }
}

回到顶部

常量

Constants

风格 03-02

Style 03-02

坚持用 const 声明变量，除非它们的值在应用的生命周期内会发生变化。

Do declare variables with const if their values should not change during the application lifetime.

为何？告诉读者这个值是不可变的。

Why? Conveys to readers that the value is invariant.

为何？ TypeScript 会要求在声明时立即初始化，并阻止再次赋值，以帮助确保你的设计意图。

Why? TypeScript helps enforce that intent by requiring immediate initialization and by preventing subsequent re-assignment.

考虑把常量名拼写为小驼峰格式。

Consider spelling const variables in lower camel case.

为何？小驼峰变量名 (heroRoutes) 比传统的大写蛇形命名法 (HERO_ROUTES) 更容易阅读和理解。

Why? Lower camel case variable names (heroRoutes) are easier to read and understand than the traditional UPPER_SNAKE_CASE names (HERO_ROUTES).

为何？ 把常量命名为大写蛇形命名法的传统源于现代 IDE 出现之前，以便阅读时可以快速发现那些 const 定义。 TypeScript 本身就能够防止意外赋值。

Why? The tradition of naming constants in UPPER_SNAKE_CASE reflects an era before the modern IDEs that quickly reveal the const declaration. TypeScript prevents accidental reassignment.

坚持容许现存的const 常量沿用大写蛇形命名法。

Do tolerate existing const variables that are spelled in UPPER_SNAKE_CASE.

为何？传统的大写蛇形命名法仍然很流行、很普遍，特别是在第三方模块中。修改它们没多大价值，还会有破坏现有代码和文档的风险。

Why? The tradition of UPPER_SNAKE_CASE remains popular and pervasive, especially in third party modules. It is rarely worth the effort to change them at the risk of breaking existing code and documentation.

app/shared/data.service.ts

      
      export const mockHeroes   = ['Sam', 'Jill']; // prefer
export const heroesUrl    = 'api/heroes';    // prefer
export const VILLAINS_URL = 'api/villains';  // tolerate

回到顶部

接口

Interfaces

风格 03-03

Style 03-03

坚持使用大写驼峰命名法来命名接口。

Do name an interface using upper camel case.

考虑不要在接口名字前面加 I 前缀。

Consider naming an interface without an I prefix.

考虑在服务和可声明对象（组件、指令和管道）中用类代替接口。

Consider using a class instead of an interface for services and declarables (components, directives, and pipes).

考虑用接口作为数据模型。

Consider using an interface for data models.

为何？TypeScript 指导原则不建议使用 “I” 前缀。

Why? TypeScript guidelines discourage the I prefix.

为何？单独一个类的代码量小于类+接口。

Why? A class alone is less code than a class-plus-interface.

为何？类可以作为接口使用（只是用 implements 代替 extends 而已）。

Why? A class can act as an interface (use implements instead of extends).

为何？在 Angular 依赖注入系统中，接口类（译注：指写成类的形式，但是只当做接口使用）可以作为服务提供商的查找令牌。

Why? An interface-class can be a provider lookup token in Angular dependency injection.

app/shared/hero-collector.service.ts

      
      /* avoid */
 
import { Injectable } from '@angular/core';
 
import { IHero } from './hero.model.avoid';
 
@Injectable()
export class HeroCollectorService {
  hero: IHero;
 
  constructor() { }
}

app/shared/hero-collector.service.ts

      
      import { Injectable } from '@angular/core';

import { Hero } from './hero.model';

@Injectable()
export class HeroCollectorService {
  hero: Hero;

  constructor() { }
}

回到顶部

属性和方法

Properties and methods

样式 03-04

Style 03-04

坚持使用小写驼峰命名法来命名属性和方法。

Do use lower camel case to name properties and methods.

避免为私有属性和方法添加下划线前缀。

Avoid prefixing private properties and methods with an underscore.

为何？遵循传统属性和方法的命名约定。

Why? Follows conventional thinking for properties and methods.

为何？ JavaScript 不支持真正的私有属性和方法。

Why? JavaScript lacks a true private property or method.

为何？ TypeScript 工具让识别私有或公有属性和方法变得很简单。

Why? TypeScript tooling makes it easy to identify private vs. public properties and methods.

app/shared/toast.service.ts

      
      /* avoid */
 
import { Injectable } from '@angular/core';
 
@Injectable()
export class ToastService {
  message: string;
 
  private _toastCount: number;
 
  hide() {
    this._toastCount--;
    this._log();
  }
 
  show() {
    this._toastCount++;
    this._log();
  }
 
  private _log() {
    console.log(this.message);
  }
}

app/shared/toast.service.ts

      
      import { Injectable } from '@angular/core';
 
@Injectable()
export class ToastService {
  message: string;
 
  private toastCount: number;
 
  hide() {
    this.toastCount--;
    this.log();
  }
 
  show() {
    this.toastCount++;
    this.log();
  }
 
  private log() {
    console.log(this.message);
  }
}

回到顶部

导入语句中的空行

Import line spacing

风格 03-06

Style 03-06

坚持在第三方导入和应用导入之间留一个空行。

Consider leaving one empty line between third party imports and application imports.

考虑按模块名字的字母顺排列导入行。

Consider listing import lines alphabetized by the module.

考虑在解构表达式中按字母顺序排列导入的东西。

Consider listing destructured imported symbols alphabetically.

为何？空行可以让阅读和定位本地导入更加容易。

Why? The empty line separates your stuff from their stuff.

为何？按字母顺序排列可以让阅读和定位本地导入更加容易。

Why? Alphabetizing makes it easier to read and locate symbols.

app/heroes/shared/hero.service.ts

      
      /* avoid */

import { ExceptionService, SpinnerService, ToastService } from '../../core';
import { HttpClient } from '@angular/common/http';
import { Injectable } from '@angular/core';
import { Hero } from './hero.model';

app/heroes/shared/hero.service.ts

      
      import { HttpClient } from '@angular/common/http';
import { Injectable } from '@angular/core';

import { ExceptionService, SpinnerService, ToastService } from '../../core';
import { Hero } from './hero.model';

回到顶部

应用程序结构与 NgModule

Application structure and NgModules

准备一个近期实施方案和一个长期的愿景。从零开始，但要考虑应用程序接下来的路往哪儿走。

Have a near-term view of implementation and a long-term vision. Start small but keep in mind where the app is heading down the road.

所有应用程序的源代码都放到名叫 src 的目录里。所有特性区都在自己的文件夹中，带有它们自己的 NgModule。

All of the app's code goes in a folder named src. All feature areas are in their own folder, with their own NgModule.

所有内容都遵循每个文件一个特性的原则。每个组件、服务和管道都在自己的文件里。所有第三方程序包保存到其它目录里，而不是 src 目录。你不会修改它们，所以不希望它们弄乱你的应用程序。使用本指南介绍的文件命名约定。

All content is one asset per file. Each component, service, and pipe is in its own file. All third party vendor scripts are stored in another folder and not in the src folder. You didn't write them and you don't want them cluttering src. Use the naming conventions for files in this guide.

回到顶部

LIFT

风格 04-01

Style 04-01

坚持组织应用的结构，力求：快速定位 (Locate) 代码、一眼识别 (Identify) 代码、尽量保持扁平结构 (Flattest) 和尝试 (Try) 遵循 DRY (Do Not Repeat Yourself, 不重复自己) 原则。

Do structure the app such that you can Locate code quickly, Identify the code at a glance, keep the Flattest structure you can, and Try to be DRY.

坚持四项基本原则定义文件结构，上面的原则是按重要顺序排列的。

Do define the structure to follow these four basic guidelines, listed in order of importance.

为何？LIFT 提供了一致的结构，它具有扩展性强、模块化的特性。因为容易快速锁定代码，提高了开发者的效率。另外，检查应用结构是否合理的方法是问问自己：我能快速打开与此特性有关的所有文件并开始工作吗？

Why? LIFT Provides a consistent structure that scales well, is modular, and makes it easier to increase developer efficiency by finding code quickly. To confirm your intuition about a particular structure, ask: can I quickly open and start work in all of the related files for this feature?

回到顶部

定位

Locate

风格 04-02

Style 04-02

坚持直观、简单和快速地定位代码。

Do make locating code intuitive, simple and fast.

为何？ 要想高效的工作，就必须能迅速找到文件，特别是当不知道（或不记得）文件名时。把相关的文件一起放在一个直观的位置可以节省时间。富有描述性的目录结构会让你和后面的维护者眼前一亮。

Why? To work efficiently you must be able to find files quickly, especially when you do not know (or do not remember) the file names. Keeping related files near each other in an intuitive location saves time. A descriptive folder structure makes a world of difference to you and the people who come after you.

回到顶部

识别

Identify

风格 04-03

Style 04-03

坚持命名文件到这个程度：看到名字立刻知道它包含了什么，代表了什么。

Do name the file such that you instantly know what it contains and represents.

坚持文件名要具有说明性，确保文件中只包含一个组件。

Do be descriptive with file names and keep the contents of the file to exactly one component.

避免创建包含多个组件、服务或者混合体的文件。

Avoid files with multiple components, multiple services, or a mixture.

为何？花费更少的时间来查找和琢磨代码，就会变得更有效率。较长的文件名远胜于较短却容易混淆的缩写名。

Why? Spend less time hunting and pecking for code, and become more efficient. Longer file names are far better than short-but-obscure abbreviated names.

当你有一组小型、紧密相关的特性时，违反一物一文件的规则可能会更好，这种情况下单一文件可能会比多个文件更容易发现和理解。注意这个例外。

It may be advantageous to deviate from the one-thing-per-file rule when you have a set of small, closely-related features that are better discovered and understood in a single file than as multiple files. Be wary of this loophole.

回到顶部

扁平

Flat

风格 04-04

Style 04-04

坚持尽可能保持扁平的目录结构。

Do keep a flat folder structure as long as possible.

考虑当同一目录下达到 7 个或更多个文件时创建子目录。

Consider creating sub-folders when a folder reaches seven or more files.

考虑配置 IDE，以隐藏无关的文件，例如生成出来的 .js 文件和 .js.map 文件等。

Consider configuring the IDE to hide distracting, irrelevant files such as generated .js and .js.map files.

为何？没人想要在超过七层的目录中查找文件。扁平的结构有利于搜索。

Why? No one wants to search for a file through seven levels of folders. A flat structure is easy to scan.

另一方面，心理学家们相信，当关注的事物超过 9 个时，人类就会开始感到吃力。所以，当一个文件夹中的文件有 10 个或更多个文件时，可能就是创建子目录的时候了。

On the other hand, psychologists believe that humans start to struggle when the number of adjacent interesting things exceeds nine. So when a folder has ten or more files, it may be time to create subfolders.

还是根据你自己的舒适度而定吧。除非创建新文件夹能有显著的价值，否则尽量使用扁平结构。

Base your decision on your comfort level. Use a flatter structure until there is an obvious value to creating a new folder.

回到顶部

T-DRY（尽量不重复自己）

T-DRY (Try to be DRY)

风格 04-05

Style 04-05

坚持 DRY（Don't Repeat Yourself，不重复自己）。

Do be DRY (Don't Repeat Yourself).

避免过度 DRY，以致牺牲了阅读性。

Avoid being so DRY that you sacrifice readability.

为何？虽然 DRY 很重要，但如果要以牺牲 LIFT 的其它原则为代价，那就不值得了。这也就是为什么它被称为 T-DRY。例如，把组件命名为 hero-view.component.html 是多余的，因为带有 .html 扩展名的文件显然就是一个视图 (view)。但如果它不那么显著，或不符合常规，就把它写出来。

Why? Being DRY is important, but not crucial if it sacrifices the other elements of LIFT. That's why it's called T-DRY. For example, it's redundant to name a template hero-view.component.html because with the .html extension, it is obviously a view. But if something is not obvious or departs from a convention, then spell it out.

回到顶部

总体结构的指导原则

Overall structural guidelines

风格 04-06

Style 04-06

坚持从零开始，但要考虑应用程序接下来的路往哪儿走。

Do start small but keep in mind where the app is heading down the road.

坚持有一个近期实施方案和一个长期的愿景。

Do have a near term view of implementation and a long term vision.

坚持把所有源代码都放到名为 src 的目录里。

Do put all of the app's code in a folder named src.

坚持如果组件具有多个伴生文件 (.ts、.html、.css 和 .spec)，就为它创建一个文件夹。

Consider creating a folder for a component when it has multiple accompanying files (.ts, .html, .css and .spec).

为何？ 在早期阶段能够帮助保持应用的结构小巧且易于维护，这样当应用增长时就容易进化了。

Why? Helps keep the app structure small and easy to maintain in the early stages, while being easy to evolve as the app grows.

为何? 组件通常有四个文件 (*.html、 *.css、 *.ts 和 *.spec.ts)，它们很容易把一个目录弄乱。

Why? Components often have four files (e.g. *.html, *.css, *.ts, and *.spec.ts) and can clutter a folder quickly.

下面是符合规范的目录和文件结构

Here is a compliant folder and file structure:

src

app

core

core.module.ts

exception.service.ts|spec.ts

user-profile.service.ts|spec.ts

heroes

hero

hero.component.ts|html|css|spec.ts

hero-list

hero-list.component.ts|html|css|spec.ts

shared

hero-button.component.ts|html|css|spec.ts

hero.model.ts

hero.service.ts|spec.ts

heroes.component.ts|html|css|spec.ts

heroes.module.ts

heroes-routing.module.ts

shared

shared.module.ts

init-caps.pipe.ts|spec.ts

text-filter.component.ts|spec.ts

text-filter.service.ts|spec.ts

villains

villain

...

villain-list

...

shared

...

villains.component.ts|html|css|spec.ts

villains.module.ts

villains-routing.module.ts

app.component.ts|html|css|spec.ts

app.module.ts

app-routing.module.ts

main.ts

index.html

...

node_modules/...

...

把组件放在专用目录中的方式广受欢迎，对于小型应用，还可以保持组件扁平化（而不是放在专用目录中）。这样会把四个文件放在现有目录中，也会减少目录的嵌套。无论你如何选择，请保持一致。

While components in dedicated folders are widely preferred, another option for small apps is to keep components flat (not in a dedicated folder). This adds up to four files to the existing folder, but also reduces the folder nesting. Whatever you choose, be consistent.

回到顶部

按特性组织的目录结构

Folders-by-feature structure

风格 04-07

Style 04-07

坚持根据特性区命名目录。

Do create folders named for the feature area they represent.

为何？开发人员可以快速定位代码，扫一眼就能知道每个文件代表什么，目录尽可能保持扁平，既没有重复也没有多余的名字。

Why? A developer can locate the code and identify what each file represents at a glance. The structure is as flat as it can be and there are no repetitive or redundant names.

为何？ LIFT 原则中包含了所有这些。

Why? The LIFT guidelines are all covered.

为何？遵循 LIFT 原则精心组织内容，避免应用变得杂乱无章。

Why? Helps reduce the app from becoming cluttered through organizing the content and keeping them aligned with the LIFT guidelines.

为何？当有很多文件时（例如 10 个以上），在专用目录型结构中定位它们会比在扁平结构中更容易。

Why? When there are a lot of files, for example 10+, locating them is easier with a consistent folder structure and more difficult in a flat structure.

坚持为每个特性区创建一个 NgModule。

Do create an NgModule for each feature area.

为何？ NgModule 使惰性加载可路由的特性变得更容易。

Why? NgModules make it easy to lazy load routable features.

为何？ NgModule 隔离、测试和复用特性更容易。

Why? NgModules make it easier to isolate, test, and reuse features.

点这里查看目录和文件结构的范例

Refer to this folder and file structure example.

回到顶部

应用的根模块

App root module

风格 04-08

Style 04-08

坚持在应用的根目录创建一个 NgModule（例如 /src/app）。

Do create an NgModule in the app's root folder, for example, in /src/app.

为何？每个应用都至少需要一个根 NgModule。

Why? Every app requires at least one root NgModule.

考虑把根模块命名为 app.module.ts。

Consider naming the root module app.module.ts.

为何？能让定位和识别根模块变得更容易。

Why? Makes it easier to locate and identify the root module.

app/app.module.ts

      
      import { NgModule }      from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
 
import { AppComponent }    from './app.component';
import { HeroesComponent } from './heroes/heroes.component';
 
@NgModule({
  imports: [
    BrowserModule,
  ],
  declarations: [
    AppComponent,
    HeroesComponent
  ],
  exports: [ AppComponent ],
  entryComponents: [ AppComponent ]
})
export class AppModule {}

回到顶部

特性模块

Feature modules

风格 04-09

Style 04-09

坚持为应用中每个明显的特性创建一个 NgModule。

Do create an NgModule for all distinct features in an application; for example, a Heroes feature.

坚持把特性模块放在与特性区同名的目录中（例如 app/heroes）。

Do place the feature module in the same named folder as the feature area; for example, in app/heroes.

坚持特性模块的文件名应该能反映出特性区的名字和目录（例如 app/heroes/heroes.module.ts）。

Do name the feature module file reflecting the name of the feature area and folder; for example, app/heroes/heroes.module.ts.

坚持特性模块的符号名应该能反映出特性区、目录和文件名（例如在 app/heroes/heroes.module.ts 中定义 HeroesModule）。

Do name the feature module symbol reflecting the name of the feature area, folder, and file; for example, app/heroes/heroes.module.ts defines HeroesModule.

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

Why? A feature module can expose or hide its implementation from other modules.

为何？特性模块标记出组成该特性分区的相关组件集合。

Why? A feature module identifies distinct sets of related components that comprise the feature area.

为何？方便路由到特性模块 —— 无论是用主动加载还是惰性加载的方式。

Why? A feature module can easily be routed to both eagerly and lazily.

为何？特性模块在特定的功能和其它应用特性之间定义了清晰的边界。

Why? A feature module defines clear boundaries between specific functionality and other application features.

为何？特性模块帮助澄清开发职责，以便于把这些职责指派给不同的项目组。

Why? A feature module helps clarify and make it easier to assign development responsibilities to different teams.

为何？特性模块易于隔离，以便测试。

Why? A feature module can easily be isolated for testing.

回到顶部

共享特性模块

Shared feature module

风格 04-10

Style 04-10

坚持在 shared 目录中创建名叫 SharedModule 的特性模块（例如在 app/shared/shared.module.ts 中定义 SharedModule）。

Do create a feature module named SharedModule in a shared folder; for example, app/shared/shared.module.ts defines SharedModule.

坚持在共享模块中声明那些可能被特性模块引用的可复用组件、指令和管道。

Do declare components, directives, and pipes in a shared module when those items will be re-used and referenced by the components declared in other feature modules.

考虑把可能在整个应用中到处引用的模块命名为 SharedModule

Consider using the name SharedModule when the contents of a shared module are referenced across the entire application.

考虑不要在共享模块中提供服务。服务通常是单例的，应该在整个应用或一个特定的特性模块中只有一份。不过也有例外，比如，在下面的范例代码中，注意 SharedModule 提供了 FilterTextService。这里可以这么做，因为该服务是无状态的，也就是说，该服务的消费者不会受到这些新实例的影响。

Consider not providing services in shared modules. Services are usually singletons that are provided once for the entire application or in a particular feature module. There are exceptions, however. For example, in the sample code that follows, notice that the SharedModule provides FilterTextService. This is acceptable here because the service is stateless;that is, the consumers of the service aren't impacted by new instances.

坚持在 SharedModule 中导入所有模块都需要的资产（例如 CommonModule 和 FormsModule）。

Do import all modules required by the assets in the SharedModule; for example, CommonModule and FormsModule.

为何？ SharedModule 中包含的组件、指令和管道可能需要来自其它公共模块的特性（例如来自 CommonModule 中的 ngFor 指令）。

Why? SharedModule will contain components, directives and pipes that may need features from another common module; for example, ngFor in CommonModule.

坚持在 SharedModule 中声明所有组件、指令和管道。

Do declare all components, directives, and pipes in the SharedModule.

坚持从 SharedModule 中导出其它特性模块所需的全部符号。

Do export all symbols from the SharedModule that other feature modules need to use.

为何？ SharedModule 的存在，能让常用的组件、指令和管道在很多其它模块的组件模板中都自动可用。

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

避免在 SharedModule 中指定应用级的单例服务提供商。如果是刻意要得到多个服务单例也行，不过还是要小心。

Avoid specifying app-wide singleton providers in a SharedModule. Intentional singletons are OK. Take care.

为何？惰性加载的特性模块如果导入了这个共享模块，会创建一份自己的服务副本，这可能会导致意料之外的后果。

Why? A lazy loaded feature module that imports that shared module will make its own copy of the service and likely have undesirable results.

为何？对于单例服务，你不希望每个模块都有自己的实例。而如果 SharedModule 提供了一个服务，那就有可能发生这种情况。

Why? You don't want each module to have its own separate instance of singleton services. Yet there is a real danger of that happening if the SharedModule provides a service.

src

app

shared

shared.module.ts

init-caps.pipe.ts|spec.ts

text-filter.component.ts|spec.ts

text-filter.service.ts|spec.ts

app.component.ts|html|css|spec.ts

app.module.ts

app-routing.module.ts

main.ts

index.html

...

import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { FormsModule } from '@angular/forms'; import { FilterTextComponent } from './filter-text/filter-text.component'; import { FilterTextService } from './filter-text/filter-text.service'; import { InitCapsPipe } from './init-caps.pipe'; @NgModule({ imports: [CommonModule, FormsModule], declarations: [ FilterTextComponent, InitCapsPipe ], providers: [FilterTextService], exports: [ CommonModule, FormsModule, FilterTextComponent, InitCapsPipe ] }) export class SharedModule { }

import { Pipe, PipeTransform } from '@angular/core'; @Pipe({ name: 'initCaps' }) export class InitCapsPipe implements PipeTransform { transform = (value: string) => value; }

import { Component, EventEmitter, Output } from '@angular/core'; @Component({ selector: 'toh-filter-text', template: '<input type="text" id="filterText" [(ngModel)]="filter" (keyup)="filterChanged($event)" />' }) export class FilterTextComponent { @Output() changed: EventEmitter<string>; filter: string; constructor() { this.changed = new EventEmitter<string>(); } clear() { this.filter = ''; } filterChanged(event: any) { event.preventDefault(); console.log(`Filter Changed: ${this.filter}`); this.changed.emit(this.filter); } }

import { Injectable } from '@angular/core'; @Injectable() export class FilterTextService { constructor() { console.log('Created an instance of FilterTextService'); } filter(data: string, props: Array<string>, originalList: Array<any>) { let filteredList: any[]; if (data && props && originalList) { data = data.toLowerCase(); let filtered = originalList.filter(item => { let match = false; for (let prop of props) { if (item[prop].toString().toLowerCase().indexOf(data) > -1) { match = true; break; } }; return match; }); filteredList = filtered; } else { filteredList = originalList; } return filteredList; } }

import { Component } from '@angular/core'; import { FilterTextService } from '../shared/filter-text/filter-text.service'; @Component({ selector: 'toh-heroes', templateUrl: './heroes.component.html' }) export class HeroesComponent { heroes = [ { id: 1, name: 'Windstorm' }, { id: 2, name: 'Bombasto' }, { id: 3, name: 'Magneta' }, { id: 4, name: 'Tornado' } ]; filteredHeroes = this.heroes; constructor(private filterService: FilterTextService) { } filterChanged(searchText: string) { this.filteredHeroes = this.filterService.filter(searchText, ['id', 'name'], this.heroes); } }

<div>This is heroes component</div> <ul> <li *ngFor="let hero of filteredHeroes"> {{hero.name}} </li> </ul> <toh-filter-text (changed)="filterChanged($event)"></toh-filter-text>

app/shared/shared.module.ts

app/shared/init-caps.pipe.ts

app/shared/filter-text/filter-text.component.ts

app/shared/filter-text/filter-text.service.ts

app/heroes/heroes.component.ts

app/heroes/heroes.component.html

      
      import { NgModule }      from '@angular/core';
import { CommonModule }  from '@angular/common';
import { FormsModule }   from '@angular/forms';
 
import { FilterTextComponent } from './filter-text/filter-text.component';
import { FilterTextService }   from './filter-text/filter-text.service';
import { InitCapsPipe }        from './init-caps.pipe';
 
@NgModule({
  imports: [CommonModule, FormsModule],
  declarations: [
    FilterTextComponent,
    InitCapsPipe
  ],
  providers: [FilterTextService],
  exports: [
    CommonModule,
    FormsModule,
    FilterTextComponent,
    InitCapsPipe
  ]
})
export class SharedModule { }

回到顶部

核心特性模块

Core feature module

风格 04-11

Style 04-11

考虑把那些数量庞大、辅助性的、只用一次的类收集到核心模块中，让特性模块的结构更清晰简明。

Consider collecting numerous, auxiliary, single-use classes inside a core module to simplify the apparent structure of a feature module.

坚持把那些“只用一次”的类收集到 CoreModule 中，并对外隐藏它们的实现细节。简化的 AppModule 会导入 CoreModule，并且把它作为整个应用的总指挥。

Consider calling the application-wide core module, CoreModule. Importing CoreModule into the root AppModule reduces its complexity and emphasizes its role as orchestrator of the application as a whole.

坚持在 core 目录下创建一个名叫 CoreModule 的特性模块（例如在 app/core/core.module.ts 中定义 CoreModule）。

Do create a feature module named CoreModule in a core folder (e.g. app/core/core.module.ts defines CoreModule).

坚持把要共享给整个应用的单例服务放进 CoreModule 中（例如 ExceptionService 和 LoggerService）。

Do put a singleton service whose instance will be shared throughout the application in the CoreModule (e.g. ExceptionService and LoggerService).

坚持导入 CoreModule 中的资产所需要的全部模块（例如 CommonModule 和 FormsModule）。

Do import all modules required by the assets in the CoreModule (e.g. CommonModule and FormsModule).

为何？ CoreModule 提供了一个或多个单例服务。Angular 使用应用的根注入器注册这些服务提供商，让每个服务的这个单例对象对所有需要它们的组件都是可用的，而不用管该组件是通过主动加载还是惰性加载的方式加载的。

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 将包含一些单例服务。而如果是由惰性加载模块来导入这些服务，它就会得到一个新实例，而不是所期望的全应用级单例。

Why? CoreModule will contain singleton services. When a lazy loaded module imports these, it will get a new instance and not the intended app-wide singleton.

坚持把应用级、只用一次的组件收集到 CoreModule 中。只在应用启动时从 AppModule 中导入它一次，以后再也不要导入它（例如 NavComponent 和 SpinnerComponent）。

Do gather application-wide, single use components in the CoreModule. Import it once (in the AppModule) when the app starts and never import it anywhere else. (e.g. NavComponent and SpinnerComponent).

为何？真实世界中的应用会有很多只用一次的组件（例如加载动画、消息浮层、模态框等），它们只会在 AppComponent 的模板中出现。不会在其它地方导入它们，所以没有共享的价值。然而它们又太大了，放在根目录中就会显得乱七八糟的。

Why? Real world apps can have several single-use components (e.g., spinners, message toasts, and modal dialogs) that appear only in the AppComponent template. They are not imported elsewhere so they're not shared in that sense. Yet they're too big and messy to leave loose in the root folder.

避免在 AppModule 之外的任何地方导入 CoreModule。

Avoid importing the CoreModule anywhere except in the AppModule.

为何？如果惰性加载的特性模块直接导入 CoreModule，就会创建它自己的服务副本，并导致意料之外的后果。

Why? A lazily loaded feature module that directly imports the CoreModule will make its own copy of services and likely have undesirable results.

为何？主动加载的特性模块已经准备好了访问 AppModule 的注入器，因此也能取得 CoreModule 中的服务。

Why? An eagerly loaded feature module already has access to the AppModule's injector, and thus the CoreModule's services.

坚持从 CoreModule 中导出 AppModule 需导入的所有符号，使它们在所有特性模块中可用。

Do export all symbols from the CoreModule that the AppModule will import and make available for other feature modules to use.

为何？CoreModule 的存在就要让常用的单例服务在所有其它模块中可用。

Why? CoreModule exists to make commonly used singleton services available for use in the many other modules.

为何？你希望整个应用都使用这个单例服务。你不希望每个模块都有这个单例服务的单独的实例。然而，如果 CoreModule 中提供了一个服务，就可能偶尔导致这种后果。

Why? You want the entire app to use the one, singleton instance. You don't want each module to have its own separate instance of singleton services. Yet there is a real danger of that happening accidentally if the CoreModule provides a service.

src

app

core

core.module.ts

logger.service.ts|spec.ts

nav

nav.component.ts|html|css|spec.ts

spinner

spinner.component.ts|html|css|spec.ts

spinner.service.ts|spec.ts

app.component.ts|html|css|spec.ts

app.module.ts

app-routing.module.ts

main.ts

index.html

...

import { NgModule } from '@angular/core'; import { BrowserModule } from '@angular/platform-browser'; import { AppComponent } from './app.component'; import { HeroesComponent } from './heroes/heroes.component'; import { CoreModule } from './core/core.module'; @NgModule({ imports: [ BrowserModule, CoreModule, ], declarations: [ AppComponent, HeroesComponent ], exports: [ AppComponent ], entryComponents: [ AppComponent ] }) export class AppModule {}

import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { LoggerService } from './logger.service'; import { NavComponent } from './nav/nav.component'; import { SpinnerComponent } from './spinner/spinner.component'; import { SpinnerService } from './spinner/spinner.service'; @NgModule({ imports: [ CommonModule // we use ngFor ], exports: [NavComponent, SpinnerComponent], declarations: [NavComponent, SpinnerComponent], providers: [LoggerService, SpinnerService] }) export class CoreModule { }

import { Injectable } from '@angular/core'; @Injectable() export class LoggerService { log(msg: string) { console.log(msg); } error(msg: string) { console.error(msg); } }

import { Component, OnInit } from '@angular/core'; @Component({ selector: 'toh-nav', templateUrl: './nav.component.html', styleUrls: ['./nav.component.css'], }) export class NavComponent implements OnInit { menuItems = [ 'Heroes', 'Villains', 'Other' ]; ngOnInit() { } constructor() { } }

<header> <div> <h4>Tour of Heroes</h4> </div> <nav> <ul> <li *ngFor="let item of menuItems"> {{item}} </li> </ul> </nav> <br/> </header>

import { Component, OnDestroy, OnInit } from '@angular/core'; import { Subscription } from 'rxjs'; import { LoggerService } from '../logger.service'; import { SpinnerState, SpinnerService } from './spinner.service'; @Component({ selector: 'toh-spinner', templateUrl: './spinner.component.html', styleUrls: ['./spinner.component.css'] }) export class SpinnerComponent implements OnDestroy, OnInit { visible = false; private spinnerStateChanged: Subscription; constructor( private loggerService: LoggerService, private spinnerService: SpinnerService ) { } ngOnInit() { console.log(this.visible); this.spinnerStateChanged = this.spinnerService.spinnerState .subscribe((state: SpinnerState) => { this.visible = state.show; this.loggerService.log(`visible=${this.visible}`); }); } ngOnDestroy() { this.spinnerStateChanged.unsubscribe(); } }

import { Injectable } from '@angular/core'; import { Subject } from 'rxjs'; export interface SpinnerState { show: boolean; } @Injectable() export class SpinnerService { private spinnerSubject = new Subject<SpinnerState>(); spinnerState = this.spinnerSubject.asObservable(); constructor() { } show() { this.spinnerSubject.next(<SpinnerState>{ show: true }); } hide() { this.spinnerSubject.next(<SpinnerState>{ show: false }); } }

app/app.module.ts

app/core/core.module.ts

app/core/logger.service.ts

app/core/nav/nav.component.ts

app/core/nav/nav.component.html

app/core/spinner/spinner.component.ts

app/core/spinner/spinner.component.html

app/core/spinner/spinner.service.ts

      
      import { NgModule }      from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
 
import { AppComponent }   from './app.component';
import { HeroesComponent } from './heroes/heroes.component';
import { CoreModule }    from './core/core.module';
 
@NgModule({
  imports: [
    BrowserModule,
    CoreModule,
  ],
  declarations: [
    AppComponent,
    HeroesComponent
  ],
  exports: [ AppComponent ],
  entryComponents: [ AppComponent ]
})
export class AppModule {}

AppModule 变得更小了，因为很多应用根部的类都被移到了其它模块中。 AppModule 变得稳定了，因为你将会往其它模块中添加特性组件和服务提供商，而不是这个 AppModule。 AppModule 把工作委托给了导入的模块，而不是亲力亲为。 AppModule 聚焦在它自己的主要任务上：作为整个应用的总指挥。

AppModule is a little smaller because many app/root classes have moved to other modules. AppModule is stable because you will add future components and providers to other modules, not this one. AppModule delegates to imported modules rather than doing work. AppModule is focused on its main task, orchestrating the app as a whole.

回到顶部

防止多次导入 `CoreModule`

Prevent re-import of the core module

风格 04-12

Style 04-12

应该只有 AppModule 才允许导入 CoreModule。

Only the root AppModule should import the CoreModule.

坚持防范多次导入 CoreModule，并通过添加守卫逻辑来尽快失败。

Do guard against reimporting of CoreModule and fail fast by adding guard logic.

为何？守卫可以阻止对 CoreModule 的多次导入。

Why? Guards against reimporting of the CoreModule.

为何？守卫会禁止创建单例服务的多个实例。

Why? Guards against creating multiple instances of assets intended to be singletons.

app/core/module-import-guard.ts

app/core/core.module.ts

      
      export function throwIfAlreadyLoaded(parentModule: any, moduleName: string) {
  if (parentModule) {
    throw new Error(`${moduleName} has already been loaded. Import Core modules in the AppModule only.`);
  }
}

回到顶部

惰性加载的目录

Lazy Loaded folders

样式 04-13

Style 04-13

某些边界清晰的应用特性或工作流可以做成惰性加载或按需加载的，而不用总是随着应用启动。

A distinct application feature or workflow may be lazy loaded or loaded on demand rather than when the application starts.

坚持把惰性加载特性下的内容放进惰性加载目录中。典型的惰性加载目录包含路由组件及其子组件以及与它们有关的那些资产和模块。

Do put the contents of lazy loaded features in a lazy loaded folder. A typical lazy loaded folder contains a routing component, its child components, and their related assets and modules.

为何？这种目录让标识和隔离这些特性内容变得更轻松。

Why? The folder makes it easy to identify and isolate the feature content.

回到顶部

永远不要直接导入惰性加载的目录

Never directly import lazy loaded folders

样式 04-14

Style 04-14

避免让兄弟模块和父模块直接导入惰性加载特性中的模块。

Avoid allowing modules in sibling and parent folders to directly import a module in a lazy loaded feature.

为何？直接导入并使用此模块会立即加载它，而原本的设计意图是按需加载它。

Why? Directly importing and using a module will load it immediately when the intention is to load it on demand.

回到顶部

Components

把组件当做元素

Components as elements

风格 05-03

Style 05-03

考虑给组件一个元素选择器，而不是属性或类选择器。

Consider giving components an element selector, as opposed to attribute or class selectors.

为何？组件有很多包含 HTML 以及可选 Angular 模板语法的模板。它们显示内容。开发人员会把组件像原生 HTML 元素和 WebComponents 一样放进页面中。

Why? components have templates containing HTML and optional Angular template syntax. They display content. Developers place components on the page as they would native HTML elements and web components.

为何？查看组件模板的 HTML 时，更容易识别一个符号是组件还是指令。

Why? It is easier to recognize that a symbol is a component by looking at the template's html.

少数情况下，你要为组件使用属性选择器，比如你要加强某个内置元素时。比如，Material Design 组件库就会对 <button mat-button> 使用这项技术。不过，你不应该在自定义组件上使用这项技术。

There are a few cases where you give a component an attribute, such as when you want to augment a built-in element. For example, Material Design uses this technique with <button mat-button>. However, you wouldn't use this technique on a custom element.

app/heroes/hero-button/hero-button.component.ts

      
      /* avoid */

@Component({
  selector: '[tohHeroButton]',
  templateUrl: './hero-button.component.html'
})
export class HeroButtonComponent {}

app/app.component.html

      
      <!-- avoid -->

<div tohHeroButton></div>

app/heroes/shared/hero-button/hero-button.component.ts

app/app.component.html

      
      @Component({
  selector: 'toh-hero-button',
  templateUrl: './hero-button.component.html'
})
export class HeroButtonComponent {}

回到顶部

把模板和样式提取到它们自己的文件

Extract templates and styles to their own files

风格 05-04

Style 05-04

坚持当超过 3 行时，把模板和样式提取到一个单独的文件。

Do extract templates and styles into a separate file, when more than 3 lines.

坚持把模板文件命名为 [component-name].component.html，其中，[component-name] 是组件名。

Do name the template file [component-name].component.html, where [component-name] is the component name.

坚持把样式文件命名为 [component-name].component.css，其中，[component-name] 是组件名。

Do name the style file [component-name].component.css, where [component-name] is the component name.

坚持指定相对于模块的 URL ，给它加上 ./ 前缀。

Do specify component-relative URLs, prefixed with ./.

为何？巨大的、内联的模板和样式表会遮盖组件的意图和实现方式，削弱可读性和可维护性。

Why? Large, inline templates and styles obscure the component's purpose and implementation, reducing readability and maintainability.

为何？在多数编辑器中，编写内联的模板和样式表时都无法使用语法提示和代码片段功能。 Angular 的 TypeScript 语言服务（即将到来）可以帮助那些编辑器在编写 HTML 模板时克服这一缺陷，但对 CSS 样式没有帮助。

Why? In most editors, syntax hints and code snippets aren't available when developing inline templates and styles. The Angular TypeScript Language Service (forthcoming) promises to overcome this deficiency for HTML templates in those editors that support it; it won't help with CSS styles.

为何？当你移动组件文件时，相对于组件的 URL 不需要修改，因为这些文件始终会在一起。

Why? A component relative URL requires no change when you move the component files, as long as the files stay together.

为何？./ 前缀是相对 URL 的标准语法，不必依赖 Angular 的特殊处理，如果没有前缀则不行。

Why? The ./ prefix is standard syntax for relative URLs; don't depend on Angular's current ability to do without that prefix.

app/heroes/heroes.component.ts

      
      /* avoid */
 
@Component({
  selector: 'toh-heroes',
  template: `
    <div>
      <h2>My Heroes</h2>
      <ul class="heroes">
        <li *ngFor="let hero of heroes | async" (click)="selectedHero=hero">
          <span class="badge">{{hero.id}}</span> {{hero.name}}
        </li>
      </ul>
      <div *ngIf="selectedHero">
        <h2>{{selectedHero.name | uppercase}} is my hero</h2>
      </div>
    </div>
  `,
  styles: [`
    .heroes {
      margin: 0 0 2em 0;
      list-style-type: none;
      padding: 0;
      width: 15em;
    }
    .heroes li {
      cursor: pointer;
      position: relative;
      left: 0;
      background-color: #EEE;
      margin: .5em;
      padding: .3em 0;
      height: 1.6em;
      border-radius: 4px;
    }
    .heroes .badge {
      display: inline-block;
      font-size: small;
      color: white;
      padding: 0.8em 0.7em 0 0.7em;
      background-color: #607D8B;
      line-height: 1em;
      position: relative;
      left: -1px;
      top: -4px;
      height: 1.8em;
      margin-right: .8em;
      border-radius: 4px 0 0 4px;
    }
  `]
})
export class HeroesComponent implements OnInit {
  heroes: Observable<Hero[]>;
  selectedHero: Hero;
 
 constructor(private heroService: HeroService) { }
 
  ngOnInit() {
    this.heroes = this.heroService.getHeroes();
  }
}

app/heroes/heroes.component.ts

app/heroes/heroes.component.html

app/heroes/heroes.component.css

      
      @Component({
  selector: 'toh-heroes',
  templateUrl: './heroes.component.html',
  styleUrls:  ['./heroes.component.css']
})
export class HeroesComponent implements OnInit {
  heroes: Observable<Hero[]>;
  selectedHero: Hero;
 
 constructor(private heroService: HeroService) { }
 
  ngOnInit() {
    this.heroes = this.heroService.getHeroes();
  }
}

回到顶部

内联输入和输出属性装饰器

Decorate input and output properties

风格 05-12

Style 05-12

坚持使用 @Input() 和 @Output()，而非 @Directive 和 @Component 装饰器的 inputs 和 outputs 属性:

Do use the @Input() and @Output() class decorators instead of the inputs and outputs properties of the @Directive and @Component metadata:

坚持把 @Input() 或者 @Output() 放到所装饰的属性的同一行。

Consider placing @Input() or @Output() on the same line as the property it decorates.

为何？易于在类里面识别哪些属性是输入属性或输出属性。

Why? It is easier and more readable to identify which properties in a class are inputs or outputs.

为何？ 如果需要重命名与 @Input 或者 @Output 关联的属性或事件名，你可以在一个位置修改。

Why? If you ever need to rename the property or event name associated with @Input or @Output, you can modify it in a single place.

为何？依附到指令的元数据声明会比较简短，更易于阅读。

Why? The metadata declaration attached to the directive is shorter and thus more readable.

为何？把装饰器放到同一行可以精简代码，同时更易于识别输入或输出属性。

Why? Placing the decorator on the same line usually makes for shorter code and still easily identifies the property as an input or output. Put it on the line above when doing so is clearly more readable.

app/heroes/shared/hero-button/hero-button.component.ts

      
      /* avoid */
 
@Component({
  selector: 'toh-hero-button',
  template: `<button></button>`,
  inputs: [
    'label'
  ],
  outputs: [
    'change'
  ]
})
export class HeroButtonComponent {
  change = new EventEmitter<any>();
  label: string;
}

app/heroes/shared/hero-button/hero-button.component.ts

      
      @Component({
  selector: 'toh-hero-button',
  template: `<button>{{label}}</button>`
})
export class HeroButtonComponent {
  @Output() change = new EventEmitter<any>();
  @Input() label: string;
}

回到顶部

避免为输入和输出属性指定别名

Avoid aliasing inputs and outputs

风格 05-13

Style 05-13

避免除非有重要目的，否则不要为输入和输出指定别名。

Avoid input and output aliases except when it serves an important purpose.

为何？同一个属性有两个名字（一个对内一个对外）很容易导致混淆。

Why? Two names for the same property (one private, one public) is inherently confusing.

为何？如果指令名也同时用作输入属性，而且指令名无法准确描述这个属性的用途时，应该使用别名。

Why? You should use an alias when the directive name is also an input property, and the directive name doesn't describe the property.

app/heroes/shared/hero-button/hero-button.component.ts

      
      /* avoid pointless aliasing */

@Component({
  selector: 'toh-hero-button',
  template: `<button>{{label}}</button>`
})
export class HeroButtonComponent {
  // Pointless aliases
  @Output('changeEvent') change = new EventEmitter<any>();
  @Input('labelAttribute') label: string;
}

app/app.component.html

      
      <!-- avoid -->

<toh-hero-button labelAttribute="OK" (changeEvent)="doSomething()">
</toh-hero-button>

app/heroes/shared/hero-button/hero-button.component.ts

app/heroes/shared/hero-button/hero-highlight.directive.ts

app/app.component.html

      
      @Component({
  selector: 'toh-hero-button',
  template: `<button>{{label}}</button>`
})
export class HeroButtonComponent {
  // No aliases
  @Output() change = new EventEmitter<any>();
  @Input() label: string;
}

回到顶部

成员顺序

Member sequence

风格 05-14

Style 05-14

坚持把属性成员放在前面，方法成员放在后面。

Do place properties up top followed by methods.

坚持先放公共成员，再放私有成员，并按照字母顺序排列。

Do place private members after public members, alphabetized.

为何？把类的成员按照统一的顺序排列，易于阅读，能立即识别出组件的哪个成员服务于何种目的。

Why? Placing members in a consistent sequence makes it easy to read and helps instantly identify which members of the component serve which purpose.

app/shared/toast/toast.component.ts

      
      /* avoid */
 
export class ToastComponent implements OnInit {
 
  private defaults = {
    title: '',
    message: 'May the Force be with you'
  };
  message: string;
  title: string;
  private toastElement: any;
 
  ngOnInit() {
    this.toastElement = document.getElementById('toh-toast');
  }
 
  // private methods
  private hide() {
    this.toastElement.style.opacity = 0;
    window.setTimeout(() => this.toastElement.style.zIndex = 0, 400);
  }
 
  activate(message = this.defaults.message, title = this.defaults.title) {
    this.title = title;
    this.message = message;
    this.show();
  }
 
  private show() {
    console.log(this.message);
    this.toastElement.style.opacity = 1;
    this.toastElement.style.zIndex = 9999;
 
    window.setTimeout(() => this.hide(), 2500);
  }
}

app/shared/toast/toast.component.ts

      
      export class ToastComponent implements OnInit {
  // public properties
  message: string;
  title: string;
 
  // private fields
  private defaults = {
    title: '',
    message: 'May the Force be with you'
  };
  private toastElement: any;
 
  // public methods
  activate(message = this.defaults.message, title = this.defaults.title) {
    this.title = title;
    this.message = message;
    this.show();
  }
 
  ngOnInit() {
    this.toastElement = document.getElementById('toh-toast');
  }
 
  // private methods
  private hide() {
    this.toastElement.style.opacity = 0;
    window.setTimeout(() => this.toastElement.style.zIndex = 0, 400);
  }
 
  private show() {
    console.log(this.message);
    this.toastElement.style.opacity = 1;
    this.toastElement.style.zIndex = 9999;
    window.setTimeout(() => this.hide(), 2500);
  }
}

回到顶部

把逻辑放到服务里

Delegate complex component logic to services

风格 05-15

Style 05-15

坚持在组件中只包含与视图相关的逻辑。所有其它逻辑都应该放到服务中。

Do limit logic in a component to only that required for the view. All other logic should be delegated to services.

坚持把可重用的逻辑放到服务中，保持组件简单，聚焦于它们预期目的。

Do move reusable logic to services and keep components simple and focused on their intended purpose.

为何？当逻辑被放置到服务里，并以函数的形式暴露时，可以被多个组件重复使用。

Why? Logic may be reused by multiple components when placed within a service and exposed via a function.

为何？在单元测试时，服务里的逻辑更容易被隔离。当组件中调用逻辑时，也很容易被模拟。

Why? Logic in a service can more easily be isolated in a unit test, while the calling logic in the component can be easily mocked.

为何？从组件移除依赖并隐藏实现细节。

Why? Removes dependencies and hides implementation details from the component.

为何？保持组件苗条、精简和聚焦。

Why? Keeps the component slim, trim, and focused.

app/heroes/hero-list/hero-list.component.ts

      
      /* avoid */
 
import { OnInit } from '@angular/core';
import { Http, Response } from '@angular/http';
 
import { Observable } from 'rxjs';
import { catchError, finalize, map } from 'rxjs/operators';
 
import { Hero } from '../shared/hero.model';
 
const heroesUrl = 'http://angular.io';
 
export class HeroListComponent implements OnInit {
  heroes: Hero[];
  constructor(private http: Http) {}
  getHeroes() {
    this.heroes = [];
    this.http.get(heroesUrl).pipe(
      map((response: Response) => <Hero[]>response.json().data),
      catchError(this.catchBadResponse),
      finalize(() => this.hideSpinner())
    ).subscribe((heroes: Hero[]) => this.heroes = heroes);
  }
  ngOnInit() {
    this.getHeroes();
  }
 
  private catchBadResponse(err: any, source: Observable<any>) {
    // log and handle the exception
    return new Observable();
  }
 
  private hideSpinner() {
    // hide the spinner
  }
}

app/heroes/hero-list/hero-list.component.ts

      
      import { Component, OnInit } from '@angular/core';
 
import { Hero, HeroService } from '../shared';
 
@Component({
  selector: 'toh-hero-list',
  template: `...`
})
export class HeroListComponent implements OnInit {
  heroes: Hero[];
  constructor(private heroService: HeroService) {}
  getHeroes() {
    this.heroes = [];
    this.heroService.getHeroes()
      .subscribe(heroes => this.heroes = heroes);
  }
  ngOnInit() {
    this.getHeroes();
  }
}

回到顶部

不要给输出属性加前缀

Don't prefix output properties

风格 05-16

Style 05-16

坚持命名事件时，不要带前缀 on。

Do name events without the prefix on.

坚持把事件处理器方法命名为 on 前缀之后紧跟着事件名。

Do name event handler methods with the prefix on followed by the event name.

为何？与内置事件命名一致，例如按钮点击。

Why? This is consistent with built-in events such as button clicks.

为何？Angular 允许另一种备选语法 on-*。如果事件的名字本身带有前缀 on，那么绑定的表达式可能是 on-onEvent。

Why? Angular allows for an alternative syntax on-*. If the event itself was prefixed with on this would result in an on-onEvent binding expression.

app/heroes/hero.component.ts

      
      /* avoid */

@Component({
  selector: 'toh-hero',
  template: `...`
})
export class HeroComponent {
  @Output() onSavedTheDay = new EventEmitter<boolean>();
}

app/app.component.html

      
      <!-- avoid -->

<toh-hero (onSavedTheDay)="onSavedTheDay($event)"></toh-hero>

app/heroes/hero.component.ts

app/app.component.html

      
      export class HeroComponent {
  @Output() savedTheDay = new EventEmitter<boolean>();
}

回到顶部

把表现层逻辑放到组件类里

Put presentation logic in the component class

风格 05-17

Style 05-17

坚持把表现层逻辑放进组件类中，而不要放在模板里。

Do put presentation logic in the component class, and not in the template.

为何？逻辑应该只出现在一个地方（组件类里）而不应分散在两个地方。

Why? Logic will be contained in one place (the component class) instead of being spread in two places.

为何？将组件的表现层逻辑放到组件类而非模板里，可以增强测试性、维护性和重复使用性。

Why? Keeping the component's presentation logic in the class instead of the template improves testability, maintainability, and reusability.

app/heroes/hero-list/hero-list.component.ts

      
      /* avoid */
 
@Component({
  selector: 'toh-hero-list',
  template: `
    <section>
      Our list of heroes:
      <hero-profile *ngFor="let hero of heroes" [hero]="hero">
      </hero-profile>
      Total powers: {{totalPowers}}<br>
      Average power: {{totalPowers / heroes.length}}
    </section>
  `
})
export class HeroListComponent {
  heroes: Hero[];
  totalPowers: number;
}

app/heroes/hero-list/hero-list.component.ts

      
      @Component({
  selector: 'toh-hero-list',
  template: `
    <section>
      Our list of heroes:
      <toh-hero *ngFor="let hero of heroes" [hero]="hero">
      </toh-hero>
      Total powers: {{totalPowers}}<br>
      Average power: {{avgPower}}
    </section>
  `
})
export class HeroListComponent {
  heroes: Hero[];
  totalPowers: number;
 
  get avgPower() {
    return this.totalPowers / this.heroes.length;
  }
}

回到顶部

指令

Directives

使用指令来增强已有元素

Use directives to enhance an element

风格 06-01

Style 06-01

坚持当你需要有表现层逻辑，但没有模板时，使用属性型指令。

Do use attribute directives when you have presentation logic without a template.

为何？属性型指令没有模板。

Why? Attribute directives don't have an associated template.

为何？一个元素可以使用多个属性型指令。

Why? An element may have more than one attribute directive applied.

app/shared/highlight.directive.ts

      
      @Directive({
  selector: '[tohHighlight]'
})
export class HighlightDirective {
  @HostListener('mouseover') onMouseEnter() {
    // do highlight work
  }
}

app/app.component.html

      
      <div tohHighlight>Bombasta</div>

回到顶部

HostListener 和 HostBinding 装饰器 vs. 组件元数据 host

HostListener/HostBinding decorators versus host metadata

风格 06-03

Style 06-03

考虑优先使用 @HostListener 和 @HostBinding，而不是 @Directive 和 @Component 装饰器的 host 属性。

Consider preferring the @HostListener and @HostBinding to the host property of the @Directive and @Component decorators.

坚持让你的选择保持一致。

Do be consistent in your choice.

为何？对于关联到 @HostBinding 的属性或关联到 @HostListener 的方法，要修改时，只需在指令类中的一个地方修改。如果使用元数据属性 host，你就得在组件类中修改属性声明的同时修改相关的元数据。

Why? The property associated with @HostBinding or the method associated with @HostListener can be modified only in a single place—in the directive's class. If you use the host metadata property, you must modify both the property/method declaration in the directive's class and the metadata in the decorator associated with the directive.

app/shared/validator.directive.ts

      
      import { Directive, HostBinding, HostListener } from '@angular/core';

@Directive({
  selector: '[tohValidator]'
})
export class ValidatorDirective {
  @HostBinding('attr.role') role = 'button';
  @HostListener('mouseenter') onMouseEnter() {
    // do work
  }
}

与不推荐的方式（host 元数据）比较一下。

Compare with the less preferred host metadata alternative.

为何？host 元数据只是一个便于记忆的名字而已，并不需要额外的 ES 导入。

Why? The host metadata is only one term to remember and doesn't require extra ES imports.

app/shared/validator2.directive.ts

      
      import { Directive } from '@angular/core';
 
@Directive({
  selector: '[tohValidator2]',
  host: {
    '[attr.role]': 'role',
    '(mouseenter)': 'onMouseEnter()'
  }
})
export class Validator2Directive {
  role = 'button';
  onMouseEnter() {
    // do work
  }
}

回到顶部

服务

Services

服务总是单例的

Services are singletons

风格 07-01

Style 07-01

坚持在同一个注入器内，把服务当做单例使用。用它们来共享数据和功能。

Do use services as singletons within the same injector. Use them for sharing data and functionality.

为何？服务是在特性范围或应用内共享方法的理想载体。

Why? Services are ideal for sharing methods across a feature area or an app.

为何？服务是共享状态性内存数据的理想载体。

Why? Services are ideal for sharing stateful in-memory data.

app/heroes/shared/hero.service.ts

      
      export class HeroService {
  constructor(private http: Http) { }

  getHeroes() {
    return this.http.get('api/heroes').pipe(
      map((response: Response) => <Hero[]>response.json()));
  }
}

回到顶部

单一职责

Single responsibility

风格 07-02

Style 07-02

坚持创建封装在上下文中的单一职责的服务。

Do create services with a single responsibility that is encapsulated by its context.

坚持当服务成长到超出单一用途时，创建一个新服务。

Do create a new service once the service begins to exceed that singular purpose.

为何？当服务有多个职责时，它很难被测试。

Why? When a service has multiple responsibilities, it becomes difficult to test.

为何？当某个服务有多个职责时，每个注入它的组件或服务都会承担这些职责的全部开销。

Why? When a service has multiple responsibilities, every component or service that injects it now carries the weight of them all.

回到顶部

提供一个服务

Providing a service

风格 07-03

Style 07-03

坚持在服务的 @Injectable 装饰器上指定通过应用的根注入器提供服务。

Do provide a service with the app root injector in the @Injectable decorator of the service.

为何？ Angular 注入器是层次化的。

Why? The Angular injector is hierarchical.

为何？当你在根注入器上提供该服务时，该服务实例在每个需要该服务的类中是共享的。当服务要共享方法或状态时，这是最理想的选择。

Why? When you provide the service to a root injector, that instance of the service is shared and available in every class that needs the service. This is ideal when a service is sharing methods or state.

为何？当你在服务的 @Injectable 中注册服务时，Angular CLI 生产环境构建时使用的优化工具可以进行摇树优化，从而移除那些你的应用中从未用过的服务。

Why? When you register a service in the @Injectable decorator of the service, optimization tools such as those used by the Angular CLI's production builds can perform tree shaking and remove services that aren't used by your app.

为何？当不同的两个组件需要一个服务的不同的实例时，上面的方法这就不理想了。在这种情况下，对于需要崭新和单独服务实例的组件，最好在组件级提供服务。

Why? This is not ideal when two different components need different instances of a service. In this scenario it would be better to provide the service at the component level that needs the new and separate instance.

src/app/treeshaking/service.ts

      
      @Injectable({
  providedIn: 'root',
})
export class Service {
}

回到顶部

使用 @Injectable() 类装饰器

Use the @Injectable() class decorator

风格 07-04

Style 07-04

坚持当使用类型作为令牌来注入服务的依赖时，使用 @Injectable() 类装饰器，而非 @Inject() 参数装饰器。

Do use the @Injectable() class decorator instead of the @Inject parameter decorator when using types as tokens for the dependencies of a service.

为何？ Angular 的 DI 机制会根据服务的构造函数参数的声明类型来解析服务的所有依赖。

Why? The Angular Dependency Injection (DI) mechanism resolves a service's own dependencies based on the declared types of that service's constructor parameters.

为何？当服务只接受类型令牌相关的依赖时，比起在每个构造函数参数上使用 @Inject()，@Injectable() 的语法简洁多了。

Why? When a service accepts only dependencies associated with type tokens, the @Injectable() syntax is much less verbose compared to using @Inject() on each individual constructor parameter.

app/heroes/shared/hero-arena.service.ts

      
      /* avoid */

export class HeroArena {
  constructor(
      @Inject(HeroService) private heroService: HeroService,
      @Inject(Http) private http: Http) {}
}

app/heroes/shared/hero-arena.service.ts

      
      @Injectable()
export class HeroArena {
  constructor(
    private heroService: HeroService,
    private http: Http) {}
}

回到顶部

数据服务

Data Services

通过服务与 Web 服务器通讯

Talk to the server through a service

风格 08-01

Style 08-01

坚持把数据操作和与数据交互的逻辑重构到服务里。

Do refactor logic for making data operations and interacting with data to a service.

坚持让数据服务来负责 XHR 调用、本地储存、内存储存或者其它数据操作。

Do make data services responsible for XHR calls, local storage, stashing in memory, or any other data operations.

为何？组件的职责是为视图展示或收集信息。它不应该关心如何获取数据，它只需要知道向谁请求数据。把如何获取数据的逻辑移动到数据服务里，简化了组件，让其聚焦于视图。

Why? The component's responsibility is for the presentation and gathering of information for the view. It should not care how it gets the data, just that it knows who to ask for it. Separating the data services moves the logic on how to get it to the data service, and lets the component be simpler and more focused on the view.

为何？在测试使用数据服务的组件时，可以让数据调用更容易被测试（模拟或者真实）。

Why? This makes it easier to test (mock or real) the data calls when testing a component that uses a data service.

为何？数据管理的详情，比如头信息、方法、缓存、错误处理和重试逻辑，不是组件和其它的数据消费者应该关心的事情。

Why? The details of data management, such as headers, HTTP methods, caching, error handling, and retry logic, are irrelevant to components and other data consumers.

数据服务应该封装这些细节。这样，在服务内部修改细节，就不会影响到它的消费者。并且更容易通过实现一个模拟服务来对消费者进行测试。

A data service encapsulates these details. It's easier to evolve these details inside the service without affecting its consumers. And it's easier to test the consumers with mock service implementations.

回到顶部

生命周期钩子

Lifecycle hooks

使用生命周期钩子来介入到 Angular 暴露的重要事件里。

Use Lifecycle hooks to tap into important events exposed by Angular.

回到顶部

实现生命周期钩子接口

Implement lifecycle hook interfaces

风格 09-01

Style 09-01

坚持实现生命周期钩子接口。

Do implement the lifecycle hook interfaces.

为何？如果使用强类型的方法签名，编译器和编辑器可以帮你揪出拼写错误。

Why? Lifecycle interfaces prescribe typed method signatures. use those signatures to flag spelling and syntax mistakes.

app/heroes/shared/hero-button/hero-button.component.ts

      
      /* avoid */

@Component({
  selector: 'toh-hero-button',
  template: `<button>OK<button>`
})
export class HeroButtonComponent {
  onInit() { // misspelled
    console.log('The component is initialized');
  }
}

app/heroes/shared/hero-button/hero-button.component.ts

      
      @Component({
  selector: 'toh-hero-button',
  template: `<button>OK</button>`
})
export class HeroButtonComponent implements OnInit {
  ngOnInit() {
    console.log('The component is initialized');
  }
}

回到顶部

附录

Appendix

有用的 Angular 工具和小提示

Useful tools and tips for Angular.

回到顶部

Codelyzer

风格 A-01

Style A-01

坚持使用 codelyzer 来实施本指南。

Do use codelyzer to follow this guide.

考虑调整 codelyzer 的规则来满足你的需求。

Consider adjusting the rules in codelyzer to suit your needs.

回到顶部

文档模板和代码片段

File templates and snippets

风格 A-02

Style A-02

坚持使用文件模板或代码片段来帮助实现一致的风格和模式。下面是为一些网络开发编辑器和 IDE 准备的模板和/或代码片段：

Do use file templates or snippets to help follow consistent styles and patterns. Here are templates and/or snippets for some of the web development editors and IDEs.

考虑使用 Visual Studio Code的代码片段来实施本风格指南。

Consider using snippets for Visual Studio Code that follow these styles and guidelines.

考虑使用 Atom 的代码片断来实施本风格指南。

Consider using snippets for Atom that follow these styles and guidelines.

考虑使用 Sublime Text的代码片断来实施本风格指南。

Consider using snippets for Sublime Text that follow these styles and guidelines.

考虑使用 Vim 的代码片断来实施本风格指南。

Consider using snippets for Vim that follow these styles and guidelines.

回到顶部

风格指南link

Style Guidelink

风格指南的用词link

Style vocabularylink

文件结构约定link

File structure conventionslink

单一职责link

Single responsibilitylink

单一规则link

Rule of Onelink

风格 01-01link

Style 01-01link

小函数link

Small functionslink

风格 01-02link

Style 01-02link

命名link

Naminglink

总体命名原则link

General Naming Guidelineslink

风格 02-01link

Style 02-01link

使用点和横杠来分隔文件名link

Separate file names with dots and dasheslink

风格 02-02link

Style 02-02link

符号名与文件名link

Symbols and file nameslink

风格 02-03link

Style 02-03link

服务名link

Service nameslink

风格 02-04link

Style 02-04link

引导link

Bootstrappinglink

风格 02-05link

Style 02-05link

组件选择器link

Component selectorslink

风格 05-02link

Style 05-02link

为组件添加自定义前缀link

Component custom prefixlink

风格 02-07link

Style 02-07link

指令选择器link

Directive selectorslink

风格 02-06link

Style 02-06link

为指令添加自定义前缀link

Directive custom prefixlink

风格 02-08link

Style 02-08link

管道名link

Pipe nameslink

风格 02-09link

Style 02-09link

单元测试文件名link

Unit test file nameslink

风格 02-10link

Style 02-10link

端到端（E2E）测试的文件名link

End-to-End (E2E) test file nameslink

风格 02-11link

Style 02-11link

Angular NgModule 命名link

Angular NgModule nameslink

风格 02-12link

Style 02-12link

编程约定link

Coding conventionslink

类link

Classeslink

风格 03-01link

Style 03-01link

常量link

Constantslink

风格 03-02link

Style 03-02link

风格指南

Style Guide

风格指南的用词

Style vocabulary

文件结构约定

File structure conventions

单一职责

Single responsibility

单一规则

Rule of One

风格 01-01

Style 01-01

小函数

Small functions

风格 01-02

Style 01-02

命名

Naming

总体命名原则

General Naming Guidelines

风格 02-01

Style 02-01

使用点和横杠来分隔文件名

Separate file names with dots and dashes

风格 02-02

Style 02-02

符号名与文件名

Symbols and file names

风格 02-03

Style 02-03

服务名

Service names

风格 02-04

Style 02-04

引导

Bootstrapping

风格 02-05

Style 02-05

组件选择器

Component selectors

风格 05-02

Style 05-02

为组件添加自定义前缀

Component custom prefix

风格 02-07

Style 02-07

指令选择器

Directive selectors

风格 02-06

Style 02-06

为指令添加自定义前缀

Directive custom prefix

风格 02-08

Style 02-08

管道名

Pipe names

风格 02-09

Style 02-09

单元测试文件名

Unit test file names

风格 02-10

Style 02-10

端到端（E2E）测试的文件名

End-to-End (E2E) test file names

风格 02-11

Style 02-11

Angular NgModule 命名

Angular NgModule names

风格 02-12

Style 02-12

编程约定

Coding conventions

类

Classes

风格 03-01

Style 03-01

常量

Constants

风格 03-02

Style 03-02