Formatting - Place Brace on new line
Posted: Wed Jun 12, 2019 2:31 pm
To help you better we need some information from you.
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product: PowerShell Studio 2019 (64 Bit)
Build: v5.6.164
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.18362.0
*** Please add details and screenshots as needed below. ***
I just updated to the latest version this week and the option to Place open brace on new line is unchecked. Despite that, it keeps putting the open brace on a new line like this:
if ($value)
{
Out-Default 'True'
} else
{
Out-Default 'False'
}
I'm wondering if it has to deal with this fix in the latest build:
FIX: Formatting would incorrectly move a script block�s open brace to a new line when it was passed to a cmdlet using a positional-based parameter and follows a close parenthesis.
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product: PowerShell Studio 2019 (64 Bit)
Build: v5.6.164
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.18362.0
*** Please add details and screenshots as needed below. ***
I just updated to the latest version this week and the option to Place open brace on new line is unchecked. Despite that, it keeps putting the open brace on a new line like this:
if ($value)
{
Out-Default 'True'
} else
{
Out-Default 'False'
}
I'm wondering if it has to deal with this fix in the latest build:
FIX: Formatting would incorrectly move a script block�s open brace to a new line when it was passed to a cmdlet using a positional-based parameter and follows a close parenthesis.
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM