PSScriptAnalyzer
PSScriptAnalyzer copied to clipboard
PowerShell
Download ScriptAnalyzer from PowerShellGallery
Apologies if I've just missed something, but I can't seem to find much in the way of documentation for implementing rules in a .NET assembly. I took a stab at...
## PR Summary Fixes #806 and #904 It is well know that PowerShell's `+=` operator always creates a new array under the hood even if the array type is not...
## PR Summary An empty catch block was found in the code and was removed as I cannot see a reason for an exception and if so I would rather...
## PR Summary Fixes #1033 by not flagging whitespace only lines (includes tabs) in AvoidTrailingWhiteSpace rule ## PR Checklist Note: Tick the boxes below that apply to this pull request...
## PR Summary A couple of tests use the OS type to make a determination as to whether there's a case sensitive file system. In some environment (say a Linux...
## PR Summary get Linux build to upload build artifacts Add additional output to assist with debugging if there is a problem ## PR Checklist - [x] [PR has a...
## PR Summary Related: #1239 In order to enable formatting corrections of this kind: `$a-join$b` --> `$a -join $b` or reducing too much whitespace but also `-split$a --> -split $a`...
## PR Summary OK, so this far from ready, but I wanted to get it out there as a suggestion. It all started with trying to work on unary operator...
From what I can tell, there's no linting rule to check if a variable is null or unassigned when it's being referenced. This would be super helpful to avoid nullref...
Reading the [UseCompatibleCommands](https://github.com/PowerShell/PSScriptAnalyzer/blob/development/RuleDocumentation/UseCompatibleCommands.md) documentation, it says the `TargetProfiles` should follow the syntax: `______` But it falls short on explaining how to get these values. So, after a little bit of...
Metadata
Owner
Metadata
Download ScriptAnalyzer from PowerShellGallery