You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
bwh-rl
added a commit
to bwh-rl/app-route
that referenced
this issue
Sep 20, 2016
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.
The text was updated successfully, but these errors were encountered: