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(badge): badge instances not being cleaned up on destroy #14265

Merged
merged 1 commit into from Nov 27, 2018

Conversation

crisbeto
Copy link
Member

Fixes the MatBadge instances not being collected once the view is destroyed. The issue comes from the fact that when an element is created through the Renderer2, Angular adds it to an index (see DebugRenderer2), however we never tell it that it should be removed.

Fixes the `MatBadge` instances not being collected once the view is destroyed. The issue comes from the fact that when an element is created through the `Renderer2`, Angular adds it to an index (see `DebugRenderer2`), however we never tell it that it should be removed.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Nov 25, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 25, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 27, 2018
@jelbourn jelbourn merged commit 031045c into angular:master Nov 27, 2018
jelbourn pushed a commit that referenced this pull request Dec 3, 2018
Fixes the `MatBadge` instances not being collected once the view is destroyed. The issue comes from the fact that when an element is created through the `Renderer2`, Angular adds it to an index (see `DebugRenderer2`), however we never tell it that it should be removed.
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
…14265)

Fixes the `MatBadge` instances not being collected once the view is destroyed. The issue comes from the fact that when an element is created through the `Renderer2`, Angular adds it to an index (see `DebugRenderer2`), however we never tell it that it should be removed.
@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 Sep 10, 2019
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 cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants