Skip to content
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.

Sign up for GitHub

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

Backport MicrosoftDocs PR 143 #1910

Merged
merged 1 commit into from
May 7, 2023
Merged

Backport MicrosoftDocs PR 143 #1910

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/Rules/PossibleIncorrectComparisonWithNull.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ This is how the comparison operator works by-design. But, as demonstrated, this
to non-intuitive behavior, especially when the intent is simple test for null.

The following example demonstrates the designed behavior of the comparison operator when the
left-hand side is a collection. Each element in the collection is compared the right-hand side
left-hand side is a collection. Each element in the collection is compared to the right-hand side
value. When true, that element of the collection is returned.

```powershell
Expand Down