Skip to content

fix(list): selection list always firing change event for selectAll and deselectAll #11029

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

Conversation

crisbeto
Copy link
Member

Currently selection list will always fire its model change event when invoking selectAll and deselectAll, even if the state of any of the options hasn't changed. These changes ensure that it only gets fired when something has changed.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 26, 2018
* Sets the selected state on all of the options
* and emits an event if anything changed.
*/
private _toggleAll(isSelected: boolean) {
Copy link
Member

Choose a reason for hiding this comment

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

How about _setAllOptionsSelected? To me "toggle" means specifically flipping from what it was before.

* and emits an event if anything changed.
*/
private _toggleAll(isSelected: boolean) {
let hasChanged = false;
Copy link
Member

Choose a reason for hiding this comment

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

Add a comment like

// Keep track of whether anything changed because we only want to emit
// a change event if something actually changed.

…d deselectAll

Currently selection list will always fire its model change event when invoking `selectAll` and `deselectAll`, even if the state of any of the options hasn't changed. These changes ensure that it only gets fired when something has changed.
@crisbeto crisbeto force-pushed the selection-list-toggle-all-events branch from 49ca718 to f1a54f1 Compare April 27, 2018 00:34
@crisbeto
Copy link
Member Author

Addressed the feedback @jelbourn.

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 target: patch This PR is targeted for the next patch release and removed pr: needs review labels Apr 27, 2018
@ngbot
Copy link

ngbot bot commented Apr 27, 2018

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure status "continuous-integration/travis-ci/pr" is failing
    pending 1 pending code review

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.

@josephperrott josephperrott removed the request for review from devversion May 1, 2018 14:53
@josephperrott josephperrott merged commit 54c0b00 into angular:master May 1, 2018
@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