Repository navigation
5.1 Hashtable Expression Parsing #23
Description
Activity
In case it's of interest, here's the original issue and fix (made in v6.1):
- Hashtable literal parsing fails when using an if statement as value PowerShell/PowerShell#6970
- Fix parser to continue parsing key-value pairs after an If-Statement value in a HashExpression PowerShell/PowerShell#7002
or you can add an else
@{ Value1 = if ($true) {'SomeValue'} else {$null} Value2 = 'OtherValue' }
Just watch out for
else { $null }. That workaround isn't equivalent to the others.When the condition is
$false, the other workarounds will result inValue1beingAutomationNull, not$null, due to statement assignment having pipeline semantics.For the
elseworkaround to be equivalent, you'd need to do this instead:@{ Value1 = if ($true) { 'SomeValue' } else {} Value2 = 'OtherValue' }
Reacted by Matthew A CargileReacted by Kris BorowinskiFor sad reasons I am not maintaining this now.
Reacted by Matthew A Cargile
In 5.1, when the key's value is an expression ( maybe only
if), you see red.whilekind of breaks with a stream of errors.foreachdoes work.try {} catch {}does not work.try {} finally {}works.This is fixed in modern PowerShell ( at least 7.6.1 ).
The above
throws the below.The workaround could be adding a semicolon
or wrapping in sub-expression operator
or you can add an
else. ( NOTE: Removing$nullinelse {}to keep the same semantics. See @surfingoldelephant's comments below.Props to @kborowinski on PowerShell Discord for discovering it. Appears the parser gets "stuck" in the "else/elseif" mode.