-
Notifications
You must be signed in to change notification settings - Fork 8.3k
$input type in advanced functions #1563
Copy link
Copy link
Closed
Labels
Breaking-Changebreaking change that may affect usersbreaking change that may affect usersCommittee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionResolution-By DesignThe reported behavior is by design.The reported behavior is by design.WG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtime
Metadata
Metadata
Assignees
Labels
Breaking-Changebreaking change that may affect usersbreaking change that may affect usersCommittee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionResolution-By DesignThe reported behavior is by design.The reported behavior is by design.WG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtime
We have a test for
$inputtype behavior in advanced functions (functions that are cmdlets).PowerShell/test/powershell/Language/Parser/AutomaticVariables.Tests.ps1
Line 3 in b731549
This tests works fine in PS v2. Since then, the behavior changed to this
Which is pretty inconsistent, but exists since v3.
@lzybkr was trying to fix it (back to v2 behavior) and it broke a couple customer scenarios.
Plan: we will gover feedback about this issue and may consider go thru breaking change process.
Meanwhile, I'm marking the test as
-Skip