Improvements: Dynamic animations, pageTransitionService, :enter and :leave animations

[bergben]

• Deprecate ng2-page-transition and rename to ngx-animate-routes

• Pass data in routes like

const routes: Routes = [
  {
    path: 'home',
    component: HomeComponent,
    data: {
      pageTransition: {
           goBackMotion: ['toRoute1'],
           goForwardMotion: ['toRoute2']
      }
    }
  },
[...]
]

• Use ActivatedRoute to get page-transition data per route and trigger transition based on fromRoutes or toRoutes or trigger default transition if no matches.

• Add service to support special use cases like

showNextFriend(someId: string):void{
     this.pageTransitionService.nextRouteDo(someTransition);
     this.router.navigate('/friend/'+someId); 
}

• Make simple :enter and :leave transitions possible (<animated-router-outlet> ? ) -> Creates router-outlet. Wrap div around component so that it is not replaced immediately on route change and the leave transition can complete -> then remove div DOM node

• pass in animations in forRoot

[bergben]

There is currently no possibility to do this in a clean way without accessing the DOM directly.

Not even extending the router-outlet would work unless replacing the whole thing.

See https://gitter.im/angular/angular?at=58ba0ed3872fc8ce62b2d34a and the messages up to ~ 10 hours before
See http://stackoverflow.com/questions/42583354/angular-2-router-wait-for-animation-to-complete-on-component-before-destroying-i

Upcoming changes for animations might change this situation. Probable date to know more is the ng-conf from 5th to 7th April https://www.ng-conf.org/

Closed for now.