PSScriptAnalyzer icon indicating copy to clipboard operation
PSScriptAnalyzer copied to clipboard

Download ScriptAnalyzer from PowerShellGallery

Results 257 PSScriptAnalyzer issues
Sort by recently updated
recently updated
newest added

As concluded here https://github.com/PowerShell/PowerShell/issues/25953 The `ValueFromPipelineByPropertyName` parameter attribute should not be used with the `ValueFromPipeline` parameter attribute because it would not have any effect (the `ValueFromPipeline` attribute overrules the `ValueFromPipelineByPropertyName`...

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...

Expected behavior ----------------- ```PowerShell # # PSScriptAnalyzerSettings.psd1 # @{ # CustomRulePath = "rules.psm1" # } Invoke-ScriptAnalyzer -Path .\test.ps1 -Settings ./PSScriptAnalyzerSettings.psd1 ``` outputs: (correct) ```none RuleName Severity ScriptName Line Message --------...

--- Before submitting a bug report: - I have reproduced this on the latest released version of PSScriptAnalyzer and VS Code PowerShell extension. - I have searched for existing issues...

### Use case: We are running [GitLab Code Quality](https://docs.gitlab.com/ci/testing/code_quality/) reports in our pipeline based on the PSScriptAnalyzer results by translating the PSScriptAnalyzer severity results to a Code Quality severity. But...

When using natural line continuation with IncreaseIndentationForFirstPipeline (or IncreaseIndentationAfterEveryPipeline) enabled and pipeline chain operators, it does not format as expected like with regular pipeline operators. Before submitting a bug report:...

**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: ```powershell Invoke-ScriptAnalyzer...

Issue - Enhancement
Up-for-Grabs