Skip to content

Conversation

@crisbeto
Copy link
Member

The MDC-based chip has a check called _isBasicChip which is called on each change detection, however its result won't change since it's based on the element's node name and a static attribute. These change resolve the value once and use a property instead.

… change detection

The MDC-based chip has a check called `_isBasicChip` which is called on each change detection, however its result won't change since it's based on the element's node name and a static attribute. These change resolve the value once and use a property instead.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Mar 26, 2020
@crisbeto crisbeto requested a review from mmalerba as a code owner March 26, 2020 22:12
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 26, 2020
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

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

LGTM

@mmalerba mmalerba added lgtm action: merge The PR is ready for merge by the caretaker labels Mar 27, 2020
@jelbourn jelbourn merged commit 262e2e4 into angular:master Mar 31, 2020
jelbourn pushed a commit that referenced this pull request Apr 6, 2020
… change detection (#18929)

The MDC-based chip has a check called `_isBasicChip` which is called on each change detection, however its result won't change since it's based on the element's node name and a static attribute. These change resolve the value once and use a property instead.

(cherry picked from commit 262e2e4)
@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 May 1, 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 cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants