We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not sure if a parameter to control this behavior. I looked but couldn't find any, correct me if I'm wrong.
Invoke-Formatter -ScriptDefinition '$object.Where({ $_.Property -eq $Value })' -Verbose
Default I would expect it not to add any space after parenthesis.
$object.Where({ $_.Property -eq $Value })
Or if default should be to add a space after the open parenthesis, I would expect it to also add one before the closing parenthesis by default too. 🙂
$object.Where( { $_.Property -eq $Value } )
Adds one space after the opening parenthesis.
$object.Where( { $_.Property -eq $Value })
> $PSVersionTable Name Value ---- ----- PSVersion 5.1.18890.1000 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.18890.1000 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 > (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() } 1.18.1
The text was updated successfully, but these errors were encountered:
See #1168 …
Best solution is to use the shorthand, .where{ statement }
.where{ statement }
Sorry, something went wrong.
No branches or pull requests
Not sure if a parameter to control this behavior. I looked but couldn't find any, correct me if I'm wrong.
Steps to reproduce
Expected behavior
Default I would expect it not to add any space after parenthesis.
Or if default should be to add a space after the open parenthesis, I would expect it to also add one before the closing parenthesis by default too. 🙂
Actual behavior
Adds one space after the opening parenthesis.
Environment data
The text was updated successfully, but these errors were encountered: