Calling router.recognize with a URL which matches the current route affects the transition.from.queryParams for subsequent transitions. I've created a PR with a failing test here.
Root cause seems related to the fact that toReadOnlyRouteInfo (source) closes over a WeakMap for ROUTE_INFOS which is then mutated on subsequent calls (including calls from router.recognize). I don't know the original intent here so I'm not sure the solution.
Calling
router.recognizewith a URL which matches the current route affects thetransition.from.queryParamsfor subsequent transitions. I've created a PR with a failing test here.Root cause seems related to the fact that
toReadOnlyRouteInfo(source) closes over a WeakMap forROUTE_INFOSwhich is then mutated on subsequent calls (including calls from router.recognize). I don't know the original intent here so I'm not sure the solution.