Skip to content

Commit 521f41c

Browse files
KirkMunroKapil Borle
authored and
Kapil Borle
committed
Update PossibleIncorrectComparisonWithNull.md (#733)
* Update PossibleIncorrectComparisonWithNull.md This is technically more accurate. PowerShell doesn't check for a $null in the array as was previously indicated. * Update PossibleIncorrectComparisonWithNull.md Revised description based on comments.
1 parent fdb0499 commit 521f41c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

RuleDocumentation/PossibleIncorrectComparisonWithNull.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@
77
To ensure that PowerShell performs comparisons correctly, the `$null` element should be on the left side of the operator.
88

99
There are a number of reasons why this should occur:
10-
* When there is an array on the left side of a null equality comparison, PowerShell will check for a `$null` IN the array rather than if the array is null.
11-
* PowerShell will perform type casting left to right, resulting in incorrect comparisons when `$null` is cast to other types.
10+
* `$null` is a scalar. When the input (left side) to an operator is a scalar value, comparison operators return a Boolean value. When the input is a collection of values, the comparison operators return any matching values, or an empty array if there are no matches in the collection. The only way to reliably check if a value is `$null` is to place `$null` on the left side of the operator so that a scalar comparison is perfomed.
11+
* PowerShell will perform type casting left to right, resulting in incorrect comparisons when `$null` is cast to other scalar types.
1212

1313
## How
1414

0 commit comments

Comments
 (0)