Generate event from Child routers instead of root router

[jsobell]

We currently have EventAggregator events raised for the router, but these are generated from and refer to the root router only.
When creating global actions relating to routers (such as context sensitive information, such as discussed in #281, we need routing information from the children too.
Given that we can easily walk up the chain of routers, it makes sense that the raised events include the information as to which is the final router instance involved in the route, as this contains all of the params from the current and parent route variables.
The only current workaround (I could find) is to add a method to the activate(params) of every VM and raise the event there.

[swiftanthony]

Same issue here. Are there any updates on this ?

[EisenbergEffect]

It sounds like we can add this pretty easily. Would anyone care to spec it out and provide a few more implementations details?

[droda59]

Same issue. The aurelia-google-analytics plugin needs the route's title to send data, but the events raised from the child router navigation doesn't include this information. @miguelzakharia

[dweber019]

I have the same issue here. I like to receive the child router route config which is currently active.

Here an example:

Given:
I have a root router with a route customers and a child router has a route /:id with the property settings configured in the route definition.

Then:
Navigate to child router route /:id.

Expect:
Event router:navigation:complete is fired and the instruction provided in the event has the instruction of the child router with the settings which have been configured.

I think only the currently active router should fire events.

This should be implemented for all events:

• router:navigation:processing
• router:navigation:error
• router:navigation:canceled
• router:navigation:success
• router:navigation:complete

[dweber019]

I found a solution for my use case. To get the setting of a child router route i can call instruction.getAllInstructions() to get all route instructions. The last instruction is then the one with the information i need.

[Alexander-Taran]

maybe can be closed?
or considered for vNext

[Alexander-Taran]

@EisenbergEffect added to vNext router use cases.
Can be closed