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): remove child outlet context from parent on deactivation #41381
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Mar 30, 2021
pullapprove
bot
requested review from
AndrewKushnir,
IgorMinar,
jelbourn and
jessicajaniuk
March 30, 2021 17:11
atscott
force-pushed
the
deactivateChildOutlet
branch
from
March 30, 2021 17:14
9f26373
to
a078698
Compare
atscott
removed request for
IgorMinar,
jelbourn,
AndrewKushnir and
jessicajaniuk
March 30, 2021 17:36
pullapprove
bot
requested review from
AndrewKushnir,
IgorMinar,
jelbourn and
jessicajaniuk
March 30, 2021 17:36
atscott
removed
the
action: review
The PR is still awaiting reviews from at least one requested reviewer
label
Mar 30, 2021
atscott
removed request for
AndrewKushnir,
IgorMinar,
jelbourn and
jessicajaniuk
March 30, 2021 17:37
atscott
force-pushed
the
deactivateChildOutlet
branch
from
March 30, 2021 17:49
a078698
to
7f56bef
Compare
…ating route When we deactivate a child route, we deactivate its outlet as well as its children. We also need to clear the stored information about the route and the associated component. If we do not, the context will keep these references and can result in reactivating an outlet that was deactivated by the previous navigation. Fixes angular#41379
atscott
force-pushed
the
deactivateChildOutlet
branch
from
March 30, 2021 18:25
7f56bef
to
4f94113
Compare
atscott
removed
action: presubmit
The PR is in need of a google3 presubmit
state: WIP
labels
Apr 1, 2021
AndrewKushnir
approved these changes
Apr 7, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
zarend
pushed a commit
that referenced
this pull request
Apr 7, 2021
…ating route (#41381) When we deactivate a child route, we deactivate its outlet as well as its children. We also need to clear the stored information about the route and the associated component. If we do not, the context will keep these references and can result in reactivating an outlet that was deactivated by the previous navigation. Fixes #41379 PR Close #41381
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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
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 we deactivate a child route, we deactivate its outlet as well as
its children. We also need to remove this context from the parent
Map
.If we do not, the parent will hold on to a reference to this deactivated
context and can result in reactivating an outlet that was deactivated by
the previous navigation.
Fixes #41379