Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(router): correctly handle string command in outlets #39728

Closed
wants to merge 1 commit into from

Conversation

atscott
Copy link
Contributor

@atscott atscott commented Nov 18, 2020

There are many places where examples use just a string for the command
in outlets. When using nested outlets, we do not correctly handle
this case, as the types and algorithm always expect an array.
This PR updates the createUrlTree algorithm to account for the
possibility of a string literal as the command for an outlet.

Fixes #18928

There are many places where examples use just a string for the command
in outlets. When using nested outlets, we do not correctly handle
this case, as the types and algorithm always expect an array.
This PR updates the `createUrlTree` algorithm to account for the
possibility of a string literal as the command for an outlet.

Fixes angular#18928
@atscott atscott added action: review The PR is still awaiting reviews from at least one requested reviewer area: router target: patch This PR is targeted for the next patch release action: presubmit The PR is in need of a google3 presubmit labels Nov 18, 2020
@ngbot ngbot bot modified the milestone: needsTriage Nov 18, 2020
@google-cla google-cla bot added the cla: yes label Nov 18, 2020
@atscott atscott requested a review from mhevery November 18, 2020 00:59
@atscott
Copy link
Contributor Author

atscott commented Nov 18, 2020

presubmit

@atscott
Copy link
Contributor Author

atscott commented Nov 19, 2020

global presubmit

@atscott atscott removed the action: presubmit The PR is in need of a google3 presubmit label Nov 19, 2020
@atscott atscott added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 20, 2020
AndrewKushnir pushed a commit that referenced this pull request Nov 20, 2020
There are many places where examples use just a string for the command
in outlets. When using nested outlets, we do not correctly handle
this case, as the types and algorithm always expect an array.
This PR updates the `createUrlTree` algorithm to account for the
possibility of a string literal as the command for an outlet.

Fixes #18928

PR Close #39728
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Dec 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: router cla: yes target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

deepest outlet path as string with nested outlets path is parsed as multiple child routes
2 participants