PowerShell / PowerShell/PSScriptAnalyzer
Private parameters are reported as unused
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Before submitting a bug report:
- Make sure you are able to repro it on the latest released version
- Perform a quick search for existing issues to check if this bug has already been reported
Steps to reproduce
Run the analyzer against this script.
Param (
[String] $private:var1
)
function Test-Second
{
# $var1 is not accessible because it was private to the script.
Write-Information -InformationAction "continue" "From script: $var1"
# $var2 is not private to the calling function so we can access it.
Write-Information -InformationAction "continue" "From caller: $var2"
}
function Test-NotGlobal
{
Param (
[String] $var2
)
$a = $var1 + " " + $var2
Write-Information -InformationAction "continue" "Concatenation: $a"
Test-Second
}
Test-NotGlobal $var1
Expected behavior
Expect no errors because $private:var1 and the use in the last line of $var1 are the same variable and $var1 is private to the script, as required.
Actual behavior
PS C:\Users\pauldsmith> Invoke-ScriptAnalyzer c:\temp\gvar.ps1
RuleName Severity ScriptName Line Message
-------- -------- ---------- ---- -------
PSReviewUnusedParameter Warning gvar.ps1 2 The parameter 'private:var1' has been declared but not
used.
PS C:\Users\pauldsmith>
If an unexpected error was thrown then please report the full error details using e.g. $error[0] | Select-Object *
Environment data
> $PSVersionTable
Name Value
---- -----
PSVersion 5.1.22621.963
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.22621.963
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
> (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }
1.21.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running Invoke-ScriptAnalyzer on the PowerShell reproduction and inspect the PSReviewUnusedParameter rule's implementation and coverage. Confirm that the private parameter and its final use are recognized as the same variable; done means the reproduction produces no unused-parameter warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100