Failing test for issue with controllerName + queryParams + transitionTo #16988
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the
controllerName
property to share a controller across a parent and child route,RouterService#transitionTo
fails when attempting to transition to the route that that is "sharing" viacontrollerName
.For example,
parent
has a controller that definesqueryParams
as['foo']
, andparent.child
usescontrollerName: 'parent'
to share the controller. Attempting to callRouterService#transitionTo('parent.child')
will throw the following error:Based on the digging I've done so far, I can tell you that this assertion is happening in
router.js
here, and appears to be failing due toparentProp
being undefined.There appears to be prior discussion/work on this issue, as seen in the following commits/issues:
However, I haven't found anything related specifically to the
controllerName
issue, though the same assertion is being triggered in all cases.Here is a twiddle that demonstrates the issue.
Fixes #14560.