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
Fix formatting in all files #1949
Conversation
@@ -95,7 +95,7 @@ | |||
# It's for rebuilding PowerShellGet (and PoshCode) NuGet-style packages | |||
# We had to do this because it's the only place we're allowed to extend the manifest | |||
# https://connect.microsoft.com/PowerShell/feedback/details/421837 | |||
PSData = @{ | |||
PSData = @{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the PSD1 formatting of hashtables is weird, but I am okay with that.
@{ | ||
Severity = @('Error','Warning') | ||
Severity = @('Error', 'Warning') | ||
IncludeDefaultRules = $true | ||
CustomRulePath = './Pester.BuildAnalyzerRules' | ||
ExcludeRules=@( | ||
CustomRulePath = './Pester.BuildAnalyzerRules' | ||
ExcludeRules = @( | ||
'PSUseShouldProcessForStateChangingFunctions' | ||
'PSUseApprovedVerbs' | ||
'Measure-SafeCommands' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here. PSD1 formatting sucks.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Since we're enabling format on save here, should we standardize on UTF8-bom encoding for ps1/psm1 files at the same time? Related #1747 With BOM due to Windows PowerShell versions. |
Sure. Moving discussion to the issue. |
Fixed formatting in all files and fixed tests that rely on formatting