Skip to content

fix(tree) make change detection less often #11103

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

Merged
merged 1 commit into from
May 3, 2018

Conversation

stasmaxymov
Copy link
Contributor

The CdkTree component calls change detection after each node insert, which has impact
on performance. The fix is to call change detection only once, when a set of nodes
is rendered.

Related bug: #11101

@stasmaxymov stasmaxymov requested a review from tinayuangao as a code owner May 2, 2018 15:59
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 2, 2018
Copy link
Contributor

@tinayuangao tinayuangao left a comment

Choose a reason for hiding this comment

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

LGTM

@tinayuangao tinayuangao added action: merge The PR is ready for merge by the caretaker pr: lgtm labels May 2, 2018
@ngbot
Copy link

ngbot bot commented May 2, 2018

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure missing required label: "target: *"

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@tinayuangao tinayuangao added the target: patch This PR is targeted for the next patch release label May 2, 2018
@@ -605,7 +605,9 @@ describe('CdkTree', () => {
try {
TestBed.createComponent(NestedCdkErrorTreeApp).detectChanges();
flush();
} catch {
} catch (e) {
Copy link
Contributor

Choose a reason for hiding this comment

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

You don't need e.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@rafaelss95, e is removed

The CdkTree component calls change detection after each node insert, which has impact
on performance. The fix is to call change detection only once, when a set of nodes
is rendered.

Related bug: angular#11101
@stasmaxymov stasmaxymov force-pushed the improve-tree-performance branch from f4b4cd9 to 0fbbe45 Compare May 3, 2018 06:41
@josephperrott josephperrott merged commit e59d0fb into angular:master May 3, 2018
@stasmaxymov stasmaxymov deleted the improve-tree-performance branch May 4, 2018 07:04
@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 8, 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.

5 participants