Skip to content

FIX: Issue-61. Don't change disable children on parent click #62

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
Sep 5, 2018
Merged

FIX: Issue-61. Don't change disable children on parent click #62

merged 1 commit into from
Sep 5, 2018

Conversation

SDSLeon
Copy link
Contributor

@SDSLeon SDSLeon commented Nov 16, 2017

#61

@jakezatecky
Copy link
Owner

jakezatecky commented Nov 21, 2017

EDIT: nevermind. I misunderstood the original intent.

Copy link
Owner

@jakezatecky jakezatecky left a comment

Choose a reason for hiding this comment

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

Thanks for the PR. If you could make that modification, I'll merge it in.

@@ -123,6 +123,7 @@ class CheckboxTree extends React.Component {

toggleChecked(node, isChecked, noCascade) {
if (node.children === null || noCascade) {
if (node.disabled) return;
Copy link
Owner

Choose a reason for hiding this comment

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

Would prefer this check to go down to where the children loop is, because the originator of the check (the parent) had to be enabled, so this check is slightly redundant for the root request.

I am also not a fan of shorthand if statements, so I would prefer the longer version with curly braces (actually surprised this is not enabled as an ESLint rule...I'll have to look into that).

jakezatecky added a commit that referenced this pull request Sep 5, 2018
@jakezatecky jakezatecky merged commit 12ddfcc into jakezatecky:master Sep 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants