issues Search Results · repo:PowerShell/PSScriptAnalyzer language:C#
Filter by
1k results
(1 s)1k results
inPowerShell/PSScriptAnalyzer (press backspace or delete to remove)Similar to the rule AvoidUsingPlainTextForPassword, passing plaintext passwords to external/binary cmdlets should be
avoided.
This includes cmdlets as e.g.:
PS C:\ Get-Command -ParameterName Password ...
iRon7
- Opened 3 days ago
- #2139
Summary of the new feature
Would be nice is PSSA could add a rule that makes sure variables are strongly typed.
Should be an optional rule, disabled by default, to not break with PowerShell default behavior. ...
o-l-a-v
- Opened 6 days ago
- #2137
I m tracking down a weird regression coming from 1.18.2 to 1.24.0.
UseCorrectCasing reports that if enabled, operators will be set to their lowercase format. But treatment of operators
seems different, ...
niphlod
- 4
- Opened 8 days ago
- #2136
Summary of the new feature
As a user of PSScriptAnalyzer, I want to be able to configure where ParameterDescription comments appear and enforce
required help sections (with optional order enforcement) ...
MariusStorhaug
- Opened 25 days ago
- #2133
Summary
Both the -Path and -ScriptDefinition parameters of Invoke-ScriptAnalyzer are [string] parameters. Both accept
ValueFromPipeline and both are declared as Position=0. While they exist in different ...
liamjpeters
- 1
- Opened on Sep 3
- #2130
As concluded here https://github.com/PowerShell/PowerShell/issues/25953
The ValueFromPipelineByPropertyName parameter attribute should not be used with the ValueFromPipeline parameter
attribute because ...
- 2
- Opened on Sep 3
- #2129
After executing the following code, the = in variable assignments are not aligned, and the = in the first hashtable are
also not aligned. I tested this in PowerShell 5.1 on Windows 10.
cls
$s = @
$hashtable ...
xhzkp
- 3
- Opened on Aug 27
- #2127
Expected behavior
# # PSScriptAnalyzerSettings.psd1
# @{
# CustomRulePath = rules.psm1
# }
Invoke-ScriptAnalyzer -Path .\test.ps1 -Settings ./PSScriptAnalyzerSettings.psd1
outputs: (correct)
RuleName ...
eissar
- Opened on Aug 23
- #2126
When using natural line continuation with IncreaseIndentationForFirstPipeline (or IncreaseIndentationAfterEveryPipeline)
enabled and pipeline chain operators, it does not format as expected like with regular ...
BrandonLake
- Opened on Aug 11
- #2120
Use case:
We are running GitLab Code Quality reports in our pipeline based on the PSScriptAnalyzer results by translating the
PSScriptAnalyzer severity results to a Code Quality severity. But it appears ...
- Opened on Aug 8
- #2118
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.