-
Notifications
You must be signed in to change notification settings - Fork 54
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
MOTECH-2618 Fixed the console error while selecting default configuration #311
base: master
Are you sure you want to change the base?
Conversation
Can one of the admins verify this patch? |
3 similar comments
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
@@ -297,7 +297,7 @@ | |||
} else { | |||
$scope.rollback = false; | |||
} | |||
} else if (newValue !== undefined && newValue.name === "") { | |||
} else if (newValue && newValue.name === "") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While at it, can we change this to (newValue && newValue.name) ? I hate these === "", they just cause issues
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pgesek we are checking whether newValue.name is empty. So, shouldn't it be (newValue && !newValue.name)?
No description provided.