Skip to content

Conversation

@crisbeto
Copy link
Member

We determine whether a node is selected in the checklist example using Array.prototype.every, but the problem is that every returns true for empty arrays which looks weird in our example.

Fixes #20085.

We determine whether a node is selected in the checklist example using `Array.prototype.every`, but the problem is that `every` returns true for empty arrays which looks weird in our example.

Fixes angular#20085.
@crisbeto crisbeto added docs This issue is related to documentation merge safe target: patch This PR is targeted for the next patch release labels Jul 27, 2020
@crisbeto crisbeto requested a review from andrewseguin as a code owner July 27, 2020 18:54
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 27, 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

this.checklistSelection.isSelected(child)
);
const descAllSelected = descendants.length > 0 && descendants.every(child => {
return this.checklistSelection.isSelected(child);
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: why add the {} and return?

Copy link
Member Author

Choose a reason for hiding this comment

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

I just find it more readable compared to the multi-line arrow function with an implicit return.

Copy link
Contributor

Choose a reason for hiding this comment

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

I prefer the implicit return, but I don't think we have an official style on way or the other

@mmalerba mmalerba added lgtm action: merge The PR is ready for merge by the caretaker labels Jul 27, 2020
@jelbourn jelbourn merged commit 75e0612 into angular:master Jul 27, 2020
jelbourn pushed a commit that referenced this pull request Jul 27, 2020
We determine whether a node is selected in the checklist example using `Array.prototype.every`, but the problem is that `every` returns true for empty arrays which looks weird in our example.

Fixes #20085.

(cherry picked from commit 75e0612)
@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 Aug 27, 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 docs This issue is related to documentation target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(MatTreeModule): Tree with checkboxes example - Reversed checkbox selected values when node has no child

4 participants