René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"-[Operator]:$false not respected in Where-Object","articleBody":"### Prerequisites\r\n\r\n- [x] Write a descriptive title.\r\n- [x] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\r\n- [x] Search the existing issues.\r\n- [x] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\r\n- [x] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://learn.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\r\n\r\n### Steps to reproduce\r\n\r\nThis is a sub-issue of #25242.\r\n\r\nThe cmdlet `Where-Object` does not respect explicit `$false` values for any of its 31 operator switch parameters. This affects all comparison and logical operator switches.\r\n\r\n**Example with `-EQ`:**\r\n\r\n```powershell\r\n$data = @(\r\n    [PSCustomObject]@{ Name = 'Alice'; Age = 25 }\r\n    [PSCustomObject]@{ Name = 'Bob'; Age = 30 }\r\n)\r\n$result = $data | Where-Object Name -EQ:$false\r\n$result.Count\r\n```\r\n\r\n**Example with `-GT`:**\r\n\r\n```powershell\r\n$result = $data | Where-Object Age -GT:$false\r\n$result.Count\r\n```\r\n\r\n### Expected behavior\r\n\r\n```console\r\nPS\u003e $result = $data | Where-Object Name -EQ:$false\r\nPS\u003e $result.Count\r\n2\r\n```\r\n\r\nWhen `-EQ:$false` is specified, the `-EQ` operator should not be active. The cmdlet should fall back to default boolean evaluation of the property value, returning all objects where `Name` is truthy (non-empty strings).\r\n\r\nSimilarly for other operators, `-[Operator]:$false` should behave as if the operator switch was not specified at all.\r\n\r\n### Actual behavior\r\n\r\n```console\r\nPS\u003e $result = $data | Where-Object Name -EQ:$false\r\nPS\u003e $result.Count\r\n0\r\n```\r\n\r\nThe `-EQ:$false` is incorrectly interpreted as `-EQ $false`, comparing the `Name` property against the boolean value `$false` instead of disabling the `-EQ` operator. This causes the filter to return no results because no `Name` values equal `$false`.\r\n\r\n### Affected parameters\r\n\r\nAll 31 operator switch parameters are affected:\r\n\r\n| Category | Parameters |\r\n|----------|------------|\r\n| Equality | `-EQ`, `-CEQ`, `-NE`, `-CNE` |\r\n| Comparison | `-GT`, `-CGT`, `-GE`, `-CGE`, `-LT`, `-CLT`, `-LE`, `-CLE` |\r\n| Pattern | `-Like`, `-CLike`, `-NotLike`, `-CNotLike`, `-Match`, `-CMatch`, `-NotMatch`, `-CNotMatch` |\r\n| Containment | `-Contains`, `-CContains`, `-NotContains`, `-CNotContains`, `-In`, `-CIn`, `-NotIn`, `-CNotIn` |\r\n| Type | `-Is`, `-IsNot` |\r\n| Logical | `-Not` |\r\n\r\n### Error details\r\n\r\nNo error is thrown. The cmdlet executes but misinterprets the explicit `$false` value as an operand rather than as a directive to disable the switch.\r\n\r\n### Environment data\r\n\r\n```powershell\r\nPS\u003e $PSVersionTable\r\n\r\nName                           Value\r\n----                           -----\r\nPSVersion                      7.5.4\r\nPSEdition                      Core\r\nGitCommitId                    7.5.4\r\nOS                             Microsoft Windows 10.0.26100\r\nPlatform                       Win32NT\r\nPSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}\r\nPSRemotingProtocolVersion      2.3\r\nSerializationVersion           1.1.0.1\r\nWSManStackVersion              3.0\r\n```\r\n\r\n### Visuals\r\n\r\n_No response_","author":{"url":"https://github.com/yotsuda","@type":"Person","name":"yotsuda"},"datePublished":"2025-11-18T23:21:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/26480/PowerShell/issues/26480"}