René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"A \"hybrid\" bareword command argument that is parsed as a number unexpectedly behaves like a string with -f (format operator)","articleBody":"### Prerequisites\n\n- [X] Write a descriptive title.\n- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\n- [X] Search the existing issues.\n- [X] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\n- [X] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://docs.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\n\n### Steps to reproduce\n\nPassing a bareword argument to a parameter that isn't type-constrained is parsed as a number if it looks like one.\r\n\r\nThe resulting value self-identifies _as a number_ and _mostly_ acts as such, but it is wrapped in an invisible `[psobject]` instance in which the original string representation is cached.\r\n\r\nIn the context of `-f`, this string representation surfaces unexpectedly, meaning that the value is unexpectedly not treated as a number:\r\n\r\n```powershell\r\n\u0026 { param($p) $p.GetType().FullName; '{0:N2}' -f $p } 0x1a\r\n```\r\n\n\n### Expected behavior\n\n```console\nSystem.Int32\r\n26.00\n```\n\n\n### Actual behavior\n\n```console\nSystem.Int32\r\n0x1a\n```\n\n\n### Error details\n\n_No response_\n\n### Environment data\n\n```powershell\nPowerShell Core 7.3.0-preview.3\n```\n\n\n### Visuals\n\n_No response_","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2022-04-26T19:58:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/17199/PowerShell/issues/17199"}