-
It will be great if there is a hyperlink in the output pointing to rule documentation for guidelines.
Invoke-ScriptAnalyzer C:\Temp\temp.ps1 | fl * -f
Line : 38
Column …
-
When I run through Invoke-ScriptAnalyzer[1], I find all of my expected violations and I see all of my custom rules running. However, when using the same settings file for Invoke-Formatter[2], it only …
-
Before submitting a bug report:
- Make sure you are able to repro it on the latest released version
- Perform a quick search for existing issues to check if this bug has already been reported
S…
-
Hyphen-minus characters are sometimes unintendedly replaced when passed by word processors as Microsoft Office applications as MSWord and Outlook. It is recommended to prefix parameters with an unamb…
-
Steps to reproduce
------------------
```powershell
function foo { param ( $a, $b, $c ) "boo" }
Invoke-ScriptAnalyzer -ScriptDefinition 'foo a b c'
```
Expected behavior
-----------------…
-
Reading the [UseCompatibleCommands](https://github.com/PowerShell/PSScriptAnalyzer/blob/development/RuleDocumentation/UseCompatibleCommands.md) documentation, it says the `TargetProfiles` should follo…
-
PSScriptAnalyzer reports **PSReservedParams** as **warning** but according to the [documentation ](https://learn.microsoft.com/en-us/powershell/utility-modules/psscriptanalyzer/rules/reservedparams?vi…
-
assignments to variables like $args and $_, etc should be caught.
see https://github.com/PowerShell/PSScriptAnalyzer/issues/265
-
**Describe the bug**
When MegaLinter runs PSScriptAnalyzer, and PSScriptAnalyzer reports no errors, MegaLinter reports that there were 12 errors.
**To Reproduce**
1. Create a GitHub repo that…
-
PSScriptAnalyzer today supports external implementation of rules in PowerShell script.
Alongside the proposal to allow custom binary rules (https://github.com/PowerShell/PSScriptAnalyzer/issues/154…