-
GET/SET/Test have identical parameters.
param
(
[Parameter(Mandatory=$true)]
[System.String]
$DistinguishedName,
[Parameter(Mandatory=$true)]
[Mi…
-
Currently the `-Fix` `-Confirm` (and `-WhatIf`) common parameters aren't very specific on what and how PSScriptAnalyzer is about to correct the found violations:
```PowerShell
invoke-scriptanalyze…
iRon7 updated
2 years ago
-
I'm occasionally getting this error on running Invoke-ScriptAnalyzer with v 1.6.0
`Invoke-ScriptAnalyzer : Cannot access a closed file.`
The Full Error Object is
``` powershell
writeErrorStream …
-
**Summary of the new feature**
When using the double quote in Chinese, PSSA should throw an error or warning.
**Proposed technical implementation details (optional)**
Three cases as follows:
…
-
**Summary of the new feature**
Currently the `-Fix` parameter is mutual exclusive with the `-ScriptDefinition` parameter:
```PowerShell
Invoke-ScriptAnalyzer -ScriptDefinition 'GCI *' -Fix
```…
-
Steps to reproduce
------------------
Unzip this: [PSScriptAnalyzer - Custom rule suppression error.zip](https://github.com/PowerShell/PSScriptAnalyzer/files/3625956/PSScriptAnalyzer.-.Custom.rule…
-
Steps to reproduce
------------------
```PowerShell
Invoke-ScriptAnalyzer -ScriptDefinition 'foreach ($Host in $foo) {}'
```
Expected behavior
-----------------
```none
The Variable 'Hos…
-
To help drive consistency for many of the tools/scripts written in PowerShell I think that we should reach some team wide consensus on Style Guidelines for PowerShell code that can be enforced as part…
-
PSSA 1.18 includes many improvements that might help DSC Resource kit.
The PSUseConsistentWhitespace could be used here and in the template to reduce PR comments.
The PSUseConsistentIndentation coul…
-
We are using PSSA as a PR policy for our repo, when the ps1 file has a code like this:
```
& "\\networkpath\\test.exe"
```
The Invoke-ScriptAnalyzer will throw a error like "Invoke-ScriptAnalyzer…