-
### Expected Behavior
`Analyze` build tasks should always return any PSScriptAnalyzer violations
### Current Behavior
In some circumstances the `Analyze` build task returns null even though indiv…
-
**Summary of the new feature**
This extension should include a setting to specify which paths to run Script Analysis against. Currently the extension reads the PSScriptAnalyzer.psd1-file in workspa…
-
### search you tried in the issue tracker
powershell, return code, exit code
### describe your issue
I'm working on a repository containing powershell scripts.
I have a pre-commit already enabled …
juju4 updated
11 months ago
-
In the default `module.tests.ps1`, the ScriptAnalyzer rules are fetched using `$scriptAnalyzerRules = Get-ScriptAnalyzerRule`.
But where should I store the `PSScriptAnalyzerSettings.psd1` file, if …
-
### Description of the new feature
Whilst developing a Powershell module that required custom interfaces, we discovered that we had to maintain back-compatibility with Powershell v5.1 (Desktop) and t…
-
From https://github.com/microsoft/msbuild/issues/2272#issuecomment-532264659
cc @rainersigwald
### Steps to reproduce
```
git clone https://github.com/PowerShell/PSScriptanalyzer
rm global.jso…
-
I really like this idea, but it made me wonder if maybe we should implement these as a set of PSScriptAnalyzer rules with built-in fixers (e.g. like the ShouldNotUseCmdletAliases one) -- this would le…
-
The required `-Path` parameter is a usability concern. It should default to `.` removing the need for the required parameter.
Is there a reason or design choice of why this parameter is required wi…
-
From https://github.com/PowerShell/PSScriptAnalyzer/pull/1476#discussion_r420669104
-
Consider an extensible model for rule severity categories.
It would be good to have another „severity“ level named „Performance“, to eventually being able to also submit rules that point to performa…