-
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 …
-
### 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
10 months ago
-
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…
-
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…
-
In a `psafile.ps1` you usually get the `PSUseDeclaredVarsMoreThanAssignments` warning, because it seems those variables are not used outside of that block. The only way to supress it is to add:
```…
-
I wish I could provide more information, but the error is transient and therefore cannot be deterministically reproed.
PowerShell version: 6.2.1
PSScriptAnalyzer version: 1.18.3
OS Version: Ubunt…
-
**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…
-
Question as per title. This would be a breaking change. What do you think @JamesWTruher