-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
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
Adding an exception to the 'newLineAfterCloseBrace' setting #576
Comments
Same issue here and I was almost filing a new issue until GitHub suggested it existed already. Verry annoying formatting: Still present in the latest insider:
Any updates if a fix would be possible? |
All of the formatting features are provided by the PSScriptAnalyzer. If this issue hasn't already been submitted to that project, please submit it there where the PSSA owners will see it. https://github.com/powershell/psscriptanalyzer |
Thank you @rkeithhill , opened a new issue here as you suggested. |
@DarkLite1 I will take a look at this issue tonight (by looking at it I think it might already be fixed in the next upcoming version of PSSA). I think we can close this issue now that the issues has been moved to PSSA |
System Details
$PSVersionTable
:Issue Description
I like the newLineAfterCloseBrace setting but I'd rather it not apply all the time. For example, in the scenario where I'm using a
where
orforeach
method. https://www.screencast.com/t/KFWP9dDE66z0This is how I'd like it to format:
However, this is how it does:
You can see that a bracket ending with a new line isn't always involved with a control statement.
The text was updated successfully, but these errors were encountered: