title: Changing root route from different module
body: <p>I feel like this should be pretty straight forward, but I can't seem to figure this out.</p>
  
  <p>I have a bunch of root routes, such as <code>login</code>, <code>events</code>, etc. I decided to create a module for my main menu, <code>MainMenuModule</code> that exports a <code>MainMenuComponent</code>, and <code>MainMenuModule</code> is imported into my root app module.</p>
  
  <pre><code>&lt;menu&gt;
      &lt;a routerLink="/"&gt;Home&lt;/a&gt;
      &lt;a routerLink="/events/"&gt;Events&lt;/a&gt;
      &lt;a routerLink="/register/"&gt;Register&lt;/a&gt;
      &lt;a routerLink="/login/"&gt;Login&lt;/a&gt;
  &lt;/menu&gt;
  </code></pre>
  
  <p>My root routing module:</p>
  
  <pre><code>import { NgModule } from '@angular/core';
  import { Routes, RouterModule } from '@angular/router';
  
  import { OrgHomeComponent } from './org-home/org-home.component';
  import { LoginComponent } from './login/login.component';
  
  const routes: Routes = [
      { path: '', component: OrgHomeComponent },
      { path: 'login', component: LoginComponent }
  ];
  
  @NgModule({
      imports: [
          RouterModule.forRoot(routes)
      ],
      exports: [
          RouterModule
      ],
      providers: []
  })
  export class AppRoutingModule { }
  </code></pre>
  
  <p>MainMenuModule has no routing; the links that are in the main menu should trigger other parts of the app.</p>
  
  <p>However, when I click on any of the links, the route doesn't change. If I include the same links straight into my root app component, it works fine, which leads me to think it's because it's in a separate module, but that doesn't really make sense to me, as links are bound to exist in nested modules/components.</p>
  
  <p>Is there something I'm missing about how routes/route links work?</p>
  
  <p>I'm generating my skeletons via angular cli if that makes a difference.</p>