Loading route not working when only optional param changes

@elitastic I think by “optional” parameters you are actually referring to unconfigured parameters. Those parameters will be put to query string ultimately. And by changing the value of querystring, you cannot trigger a transition, because there are no changes in the configured part of parameters.

However, I have revisited your earlier thread and it seems that my PR not yet fully supports the Au1 use-case. Let me find a solution for that.

In the mean time, here is an working workaround: routing within same route v2 (forked) - StackBlitz

2 Likes