diff --git a/CHANGELOG.MD b/CHANGELOG.MD index a135467d7..06d0b4b77 100644 --- a/CHANGELOG.MD +++ b/CHANGELOG.MD @@ -1,4 +1,16 @@ -## [1.14.1](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.14.1) - 2017-06-12 +## [1.15.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.15.0) - 2017-06-21 + +### Added +- (#780) `Range` parameter to the `Invoke-Formatter` cmdlet. The user can specify the range in which formatting should be applied. The primary usage for this parameter is to be used with editors that request selection formatting. +- (#782, #788) Allman style, Stroustrup style and one true brace style (OTBS) code formatting presets. +- (#790) `Kind` switch to `PSUseConsistentIndentation` rule to provide tabbed indentation. + +### Fixed +- (#781, #784) `NewLineAfer` switch behavior in `PSPlaceCloseBrace` rule. When the switch is set to `$false`, the emitted suggested corrections enforce branching control statements to be on the same line as their preceding closing braces. On the other hand when the switch is set to `$true`, the emitted suggested corrections enforce branching controls statements to be on the next line. + +Many thanks to @rkeithhill for contributing the _Stroustrup_ style code formatting preset. + +## [1.14.1](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.14.1) - 2017-06-12 ### Fixed - (#777) `Invoke-Formatter` diff --git a/Engine/PSScriptAnalyzer.psd1 b/Engine/PSScriptAnalyzer.psd1 index 3e34f3672..104579ed4 100644 --- a/Engine/PSScriptAnalyzer.psd1 +++ b/Engine/PSScriptAnalyzer.psd1 @@ -11,7 +11,7 @@ Author = 'Microsoft Corporation' RootModule = 'PSScriptAnalyzer.psm1' # Version number of this module. -ModuleVersion = '1.14.1' +ModuleVersion = '1.15.0' # ID used to uniquely identify this module GUID = 'd6245802-193d-4068-a631-8863a4342a18' @@ -87,10 +87,15 @@ PrivateData = @{ ProjectUri = 'https://github.com/PowerShell/PSScriptAnalyzer' IconUri = '' ReleaseNotes = @' +### Added +- (#780) `Range` parameter to the `Invoke-Formatter` cmdlet. The user can specify the range in which formatting should be applied. The primary usage for this parameter is to be used with editors that request selection formatting. +- (#782, #788) Allman style, Stroustrup style and one true brace style (OTBS) code formatting presets. +- (#790) `Kind` switch to `PSUseConsistentIndentation` rule to provide tabbed indentation. + ### Fixed -- (#777) `Invoke-Formatter` - - Make the cmdlet parameters positional. - - Updated documentation so that `Get-Help Invoke-Formatter -Syntax` returns a valid syntax. +- (#781, #784) `NewLineAfer` switch behavior in `PSPlaceCloseBrace` rule. When the switch is set to `$false`, the emitted suggested corrections enforce branching control statements to be on the same line as their preceding closing braces. On the other hand when the switch is set to `$true`, the emitted suggested corrections enforce branching controls statements to be on the next line. + +Many thanks to @rkeithhill for contributing the _Stroustrup_ style code formatting preset. '@ } } @@ -113,3 +118,4 @@ PrivateData = @{ + diff --git a/Engine/project.json b/Engine/project.json index d5cf0a8b9..9788b31bf 100644 --- a/Engine/project.json +++ b/Engine/project.json @@ -1,6 +1,6 @@ { "name": "Microsoft.Windows.PowerShell.ScriptAnalyzer", - "version": "1.14.1", + "version": "1.15.0", "dependencies": { "System.Management.Automation": "6.0.0-alpha13" }, diff --git a/Rules/project.json b/Rules/project.json index 4575dc07e..ad6a65d3d 100644 --- a/Rules/project.json +++ b/Rules/project.json @@ -1,9 +1,9 @@ { "name": "Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules", - "version": "1.14.1", + "version": "1.15.0", "dependencies": { "System.Management.Automation": "6.0.0-alpha13", - "Engine": "1.14.1", + "Engine": "1.15.0", "Newtonsoft.Json": "9.0.1" },