anchor.diff:    * 命令式的从一个组件导航到另一个
   
     * 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:
   
  
positive.code:   * *When the application requests navigation to the path `/crisis-center`, create or retrieve an instance of
    the `CrisisListComponent`, display its view, and update the browser's address location and history with the URL
    for that path.*
  
  .l-sub-section
  
  
negative.code: 
  <a id="Resolve"></a>
  h3#resolve-guard <i>Resolve</i>: pre-fetching component data
  h3#resolve-guard <i>解析</i>: 提前获取组件数据
  :marked
    In our `Hero Detail` and `Crisis Detail`, we waited until the route was activated to fetch our respective hero or crisis.
  
    
  
    This worked well for us, but we can always do better.
    If we were using a real world api, there may be some delay in when the data we want to display gets returned.
  