It may would be useful to get an event fired when the route was changed and the pattern matches.
Listen to activate-changed is not really an alternative, cause it only fires on first pattern match, not if an new route matches the same pattern.
It would be a more direct alternative to the routeData observers.
If the routing is more complex and more than one pattern needs to be matched, listen to changes via observers would be far more complex than listen to events.
Hi,
It may would be useful to get an event fired when the route was changed and the pattern matches. Listen to activate-changed is not really an alternative, cause it only fires on first pattern match, not if an new route matches the same pattern. It would be a more direct alternative to the routeData observers.