Upgrade UI-Router

[ghost]

Used the new router as recommended and worked around glaring gaps such as the lack of a default route, and that nested viewports do not work. We ignored the controller getting constructed twice and worked around the inability to inject $scope (beneficial side-effect of using the new router). The code itself looks needlessly complex and clumsy to extend, although it obviously aims to be the opposite of that with it's multi-stage processing pipeline. This is strike two on routers from Angular proper and it would probably benefit all to simply take the vastly superior ui-router and adopt that to Angular 1.5 and Angular 2.0. The new router has been a painful and expensive dead end. The Angular team and the community in general should view this as a problem with Angular's process and direction and be much more cautious and distrustful going forward.

[xmlking]

I burned my time trying to make new router working with nested views. Finally decided to wrap ui-router with ES7 decorators that looks like new router I.e., @RouterConfig

[fkolar]

I just experienced the same ;-(, going back to ui-router