René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Get-Item -LiteralPath with FileSystem should fail on paths with wildcards","articleBody":"If a path specified by `-LiteralPath` does not exist (or is not valid, i.e.\r\ncontains forbidden characters) then `Get-Item` should emit an error.\r\nCurrently this does not happen if a path is defined as a wildcard.\r\n\r\nThe change #4866 fixed this issue for `Remove-Item`.\r\nThe same or similar should be done for `Get-Item`.\r\n\r\n**Example:**\r\n\r\n\u003cstrike\u003eGiven items `z.*` and `[z]` do not exist\u003c/strike\u003e\r\nEDIT: Given item `[z]` does not exist. As for `z.*`, it is always \"invalid\" for `LiteralPath`.\r\n\r\n```powershell\r\nGet-Item -LiteralPath z.*\r\nGet-Item -LiteralPath [z]\r\n```\r\n\r\n**Expected result:**\r\n\r\n`Get-Item` emit errors about not found items.\r\n\r\nIn fact, an error for `z.*` may even be different, namely \"Illegal characters\r\nin the path\" because `*` or `?` are illegal for `-LiteralPath` and FileSystem.\r\n\r\n**Actual result:**\r\n\r\nThe above commands silently return nothing.\r\n","author":{"url":"https://github.com/nightroman","@type":"Person","name":"nightroman"},"datePublished":"2017-10-08T07:10:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/5057/PowerShell/issues/5057"}