RouteParams not available to top level directives

I have a primary component named Ticket which has a nested directive of TopNav

part of ticket_client;

@Component(
    selector: 'tickets'
)
@View(
    template: '<topnav></topnav><router-outlet></router-outlet>',
    directives: const [Topnav, RouterOutlet, RouteParams]
)
@RouteConfig(const [
  const Route(path: '/landing', component: Landing, as: 'landing'),
  const Route(path: '/flights', component: ViewFlights, as: 'flights'),
  const Route(path: '/contact', component: Picker, as: 'contact'),
  const Route(path: '/picker/:cityDepart/:cityArrival/:dateDepart/:dateArrival/', component: FlightDisplay, as: 'picker'),
  const Route(path: '/order/:id/:level/:dateDepart/:dateArrival/', component: ViewOrder, as: 'order'),
  const Route(path: '/order/complete', component: ViewComplete, as: 'orderComplete')
])
class Tickets {
  String name = 'Jit Ticket Application';
  Router router;

  Tickets(this.router) {
    router.subscribe( (value) {
      print("Route changed to: $value");
    });
  }
}

It exists outside of the first level router-outlet

If i try an acquire RouteParams through DI inside of TopNav - i get the following error:

Exception: No provider for RouteParams! (Topnav -> RouteParams) ExceptionHandler.call <anonymous closure>
NgZone._onErrorWithoutLongStackTrace@693253716
NgZone.<anonymous closure>

Moving topnav into the child of an outlet seems to solve the issue, but then i have to include topnav in each child view.

I would assume that RouteParams are a top level global object. Might be similar to the comments here on Angular Dart V1

http://japhr.blogspot.com/2013/10/routing-without-scope-in-angulardart.html

[ericmartinezr]

RouteData and RouteParams are provided by RouterOutlet. The only way to get access them is through routing. If you want them in some non routed component you can use services to pass the data across the app.

[aarmora]

@ericmartinezr Nice work! It took me a bit to sort through it (not by any fault of yours) but I think I got it. So the service itself is not getting the route parameters, they are coming from the routable component, to the service, which gives them to the non routable component. Brilliant!