Skip to content

fix(chips): selectionChange event firing when value has not changed #13173

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
Oct 2, 2018

Conversation

crisbeto
Copy link
Member

Fixes the selectionChange event always firing for the setter, select, deselect and selectViaInteraction, even if the value hasn't changed. Also gets rid of some repetition around emitting the event.

@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Sep 17, 2018
@crisbeto crisbeto requested a review from jelbourn as a code owner September 17, 2018 20:00
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 17, 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 modified the milestone: lgtm Sep 17, 2018
@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note labels Sep 17, 2018
@jelbourn
Copy link
Member

Caretaker note: it's possible that this will affect unit tests

@crisbeto crisbeto force-pushed the chip-unchanged-events branch from 518f1c7 to de24df0 Compare September 27, 2018 21:43
Fixes the `selectionChange` event always firing for the setter, `select`, `deselect` and `selectViaInteraction`, even if the value hasn't changed. Also gets rid of some repetition around emitting the event.
@crisbeto crisbeto force-pushed the chip-unchanged-events branch from de24df0 to 6f983fd Compare September 28, 2018 15:35
@vivian-hu-zz vivian-hu-zz merged commit e8a6ea1 into angular:master Oct 2, 2018
roboshoes pushed a commit to roboshoes/material2 that referenced this pull request Oct 23, 2018
…ngular#13173)

Fixes the `selectionChange` event always firing for the setter, `select`, `deselect` and `selectViaInteraction`, even if the value hasn't changed. Also gets rid of some repetition around emitting the event.
@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 9, 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 merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note 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