René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test-Path -Path $null should return $false","articleBody":"Test-Path will throw an error when the path is `$null` (or an empty string) instead of returning `$false`.\r\n\r\nThe errors that we do get are parameter binding errors\r\n\r\nI find myself often running into errors with `Test-Path` because of empty or `$null` strings. Then I end up making my validation more complex to account for it.\r\n\r\n```\r\nif ( Test-Path -Path $Path)\r\n{\r\n    # do something\r\n}\r\n\r\n# VS\r\n\r\nif ( $null -ne $Path -and ( Test-Path -Path $Path) )\r\n{\r\n    # do something\r\n}\r\n```\r\nIt would be nice if it would just return `$false` (or offer a `-Quiet` parameter)\r\n\r\nSteps to reproduce\r\n------------------\r\n\r\n```powershell\r\n$path = Resolve-Path -Path '.\\*\\nothing'\r\nTest-Path $path\r\n```\r\n```powershell\r\nResolve-Path -Path '.\\*\\nothing' | Test-Path\r\n```\r\n\r\nExpected behavior\r\n-----------------\r\n\r\n```none\r\nFalse\r\n```\r\n\r\nActual behavior\r\n---------------\r\n\r\n```none\r\nError: Test-Path : Cannot bind argument to parameter 'Path' because it is null.\r\n```\r\n\r\nEnvironment data\r\n----------------\r\n\r\n```powershell\r\n\u003e $PSVersionTable\r\nPSVersion                      6.1.0\r\nPSEdition                      Core\r\nGitCommitId                    6.1.0\r\nOS                             Microsoft Windows 10.0.16299\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","author":{"url":"https://github.com/KevinMarquette","@type":"Person","name":"KevinMarquette"},"datePublished":"2018-10-18T23:50:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/8076/PowerShell/issues/8076"}