René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add an -AsArray switch to ConvertTo-Json to support unconditional conversion to a JSON array","articleBody":"Based on a [suggestion by @AikenBM](https://github.com/PowerShell/PowerShell/issues/3424#issuecomment-370918077), welcomed by @SteveL-MSFT:\r\n\r\nSimilar to how `@(...)` ensures treatment of any value as an array, it would be handy if an `-AsArray` switch could instruct `ConvertTo-Json` to treat its input as an [ultimately JSON] array, so you can _guarantee that your pipeline input is treated as an array_, even if it happens to be a single item only:\r\n\r\n**Wishful thinking:**\r\n\r\n```powershell\r\n\u003e $in = 1; $in | ConvertTo-Json -AsArray\r\n[ \r\n  1 \r\n] \r\n# scalar 1 was treated as an array\r\n\r\n\u003e $in = 1, 2; $in | ConvertTo-Json -AsArray\r\n[ \r\n  1, \r\n  2 \r\n]  \r\n# Input that already is an array is left as-is\r\n```\r\n\r\n**Awkward workaround**, in the absence of `-AsArray`:\r\n\r\n```powershell\r\n\u003e $in = 1; , @($in) | ConvertTo-Json -AsArray\r\n[ \r\n  1 \r\n] \r\n```\r\n\r\n\r\nEnvironment data\r\n----------------\r\n\r\nWritten as of PowerShell Core v6.0.1","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2018-03-06T21:27:06.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/6327/PowerShell/issues/6327"}