Currently when matrix or query parameters change for a route a ROUTER_NAVIGATION action is not triggered (using @angular/router 3.4.5) because the route is already activated.
I would like to have the client state always represented in the url and would expect some type of action to be triggered (ideally a ROUTER_NAVIGATION action but it could also be something like ROUTER_PARAMS_CHANGED) when matrix or query parameters change.
Should this be a part of the router-store in order to keep the client state in sync with the url? Or is it better to be handled some other way?
Currently when matrix or query parameters change for a route a
ROUTER_NAVIGATION
action is not triggered (using @angular/router 3.4.5) because the route is already activated.I would like to have the client state always represented in the url and would expect some type of action to be triggered (ideally a
ROUTER_NAVIGATION
action but it could also be something likeROUTER_PARAMS_CHANGED
) when matrix or query parameters change.Should this be a part of the router-store in order to keep the client state in sync with the url? Or is it better to be handled some other way?