anchor.diff:    with the current instance of our `component`, the current `ActivatedRoute` and `RouterStateSnapshot` in case we needed to access
     some external information. This would be useful if we only wanted to use this guard for this component and needed to ask the component's
     properties in or to confirm whether the router should allow navigation away from it.
  +
  +  另外，我们也可以为`CrisisDetailComponent`创建一个特定的`CanDeactivate`守卫。在需要访问外部信息时，`canDeactivate`方法为提供了组件、`ActivatedRoute`和`RouterStateSnapshot`的当前实例。如果只想为这个组件使用该守卫，并且需要使用该组件属性、或者需要路由器确认是否允许从该组件导航出去时，这个守卫就非常有用。
   +makeExample('router/ts/app/can-deactivate-guard.service.1.ts', '', 'can-deactivate-guard.service.ts (component-specific)')
   
   :marked
  
positive.code:   which returns a module containing the configured `Router` service provider ... and some other,
    unseen providers that the routing library requires. We export this as the `routing` token.
  
  +makeExample('router/ts/app/app.routing.2.ts','', 'app/app.routing.ts')(format=".")
  
  .l-sub-section
  
negative.code:   * 命令式的从一个组件导航到另一个
  
    * pass information along in route parameters and subscribe to them in our component
  
    * 通过路由参数传递信息，并在组件中订阅它们。
  
    * import our feature area NgModule into our root NgModule
  
    * 在根`NgModule`中导入特征区`NgModule`。
  
    After these changes, the folder structure looks like this:
  
  