title: NativeScript: ChildActivationStart Event getting triggered causing my page to redirect
body: <p>Issue - I am on login page and click on Login button which should take me to Staff List page. However i am redirected back to login. When debugged, i saw that its happening because of ChildActivationStart.</p>
  
  <p>So navigation which should work as Login -> Staff-list
  is working as Login -> Staff-list -> Login (back due to additional Child Route Processing) navigationTrigger is shown as "hashchange" for additional route ""</p>
  
  <p>I upgraded my mobile app in NativeScript from Angular 4.4 to Angular 6.1. Post doing that, i found that there is some routing issue that has started occurring. On debugging it, i found that the issue is because of the new event ChildActivationStart that has been added while routing. </p>
  
  <p>Code to reproduce issue can be found at <a href="https://play.nativescript.org/?template=play-ng&amp;id=lrIrYT&amp;v=5" rel="nofollow noreferrer">https://play.nativescript.org/?template=play-ng&amp;id=lrIrYT&amp;v=5</a></p>
  
  <p>Here is my scenario</p>
  
  <p>app.routes.ts</p>
  
  <pre><code>export const routes: Routes = [
    { path: "",redirectTo: "authentication", pathMatch: "full" },
    { path: "authentication", component: AuthenticationComponent },
    { path: "staff-list/:id", component: StaffListComponent },
  ];
  </code></pre>
  
  <p>In my AuthenticationComponent, I do navigate to staff-list when i click on login button</p>
  
  <pre><code>export class AuthenticationComponent implements OnInit {
  constructor(
          private _router: Router
      ) {}
      //on login tap btn
      loginTap(args: EventData) {
  ....
                  this._router.navigate(['/staff-list']);
  
      }
  }
  </code></pre>
  
  <p>I have enabled the tracing for routes and here is the log that i found is as follows.</p>
  
  <pre><code>JS: Router Event: ActivationEnd
  JS: ActivationEnd(path: 'staff-list/:id')
  JS: ActivationEnd(path: 'staff-list/:id')
  JS: Router Event: ChildActivationEnd
  JS: ChildActivationEnd(path: '')
  JS: ChildActivationEnd(path: '')
  JS: Router Event: NavigationEnd
  JS: NavigationEnd(id: 2, url: '/staff-list/10', urlAfterRedirects: '/staff-list/10')
  JS: NavigationEnd(id: 2, url: '/staff-list/10', urlAfterRedirects: '/staff-list/10')
  JS: Router Event: Scroll
  JS: Scroll(anchor: 'null', position: 'null')
  JS: Scroll(anchor: 'null', position: 'null')
  JS: Router Event: NavigationStart
  JS: NavigationStart(id: 3, url: '/authentication')
  JS: NavigationStart(id: 3, url: '/authentication')
  JS: Router Event: RoutesRecognized
  JS: RoutesRecognized(id: 3, url: '/authentication', urlAfterRedirects: '/authentication', state: Route(url:'', path:'') { Route(url:'authentication', path:'authentication') } )
  JS: RoutesRecognized(id: 3, url: '/authentication', urlAfterRedirects: '/authentication', state: Route(url:'', path:'') { Route(url:'authentication', path:'authentication') } )
  JS: Router Event: GuardsCheckStart
  JS: GuardsCheckStart(id: 3, url: '/authentication', urlAfterRedirects: '/authentication', state: Route(url:'', path:'') { Route(url:'authentication', path:'authentication') } )
  JS: GuardsCheckStart(id: 3, url: '/authentication', urlAfterRedirects: '/authentication', state: Route(url:'', path:'') { Route(url:'authentication', path:'authentication') } )
  JS: Router Event: ChildActivationStart
  </code></pre>
  
  <p>Issue is occurring since ChildActivationStart with a '' route which takes it back to AuthenticationComponent.</p>
  
  <p>On checking why this behavior has occurred after upgrading to Angular 6.x, i found <a href="https://stackoverflow.com/questions/49866278/why-does-childactivationstart-event-trigger-eventhough-we-dont-have-a-child-rou">similar problem</a> reported as well but couldn't see any solution. Why does child routing events occur when we have not explicitly routed to any child links? Can this issue come because of components being in different modules? Currently structure that i have is</p>
  
  <pre><code>AppModule
      - AuthenticationModule
      - StaffModule
  </code></pre>
  
  <p>However all routing is handled via AppModule itself through app.routes.ts. This issue does not come when i downgrade Angular to 4.x version again. Can that be a probable reason for ChildRoutes getting activated? </p>