Jason Aden 66f0ab0371 fix(router): adjust ChildActivation events to only fire when the child is actually changing (#19043) ... * The problem was with the `fireChildActivationStart` function. It was taking a `path` param, which was an array of `ActivatedRouteSnapshot`s. The function was being fired for each piece of the route that was being activated. This resulted in far too many `ChildActivationStart` events being fired, and being fired on routes that weren't actually getting activated. This change fires the event only for those routes that are actually being activated. fixes #18942 PR Close #19043		2017-09-05 15:46:29 -05:00
..
index.d.ts	fix(router): adjust ChildActivation events to only fire when the child is actually changing (#19043)	2017-09-05 15:46:29 -05:00