A "hybrid" bareword command argument that is parsed as a number unexpectedly behaves like a string with -f (format operator) #17199
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
Passing a bareword argument to a parameter that isn't type-constrained is parsed as a number if it looks like one.
The 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.
In the context of -f, this string representation surfaces unexpectedly, meaning that the value is unexpectedly not treated as a number:
& { param($p) $p.GetType().FullName; '{0:N2}' -f $p } 0x1aExpected behavior
System.Int32
26.00Actual behavior
System.Int32
0x1aError details
No response
Environment data
PowerShell Core 7.3.0-preview.3Visuals
No response