PSAvoidUninitializedVariable flags automatic variables

[RamblingCookieMonster]

Hi there!

My apologies if this has already been covered.

PSAvoidUninitializedVariable seems to flag automatic PowerShell variables, such as $Matches and $PSBoundParameters.

Example code:

"hi there!" -match "hi" | Out-Null
$matches[0]

Resulting warning:

Variable 'matches' is not initialized. Non-global variables must be initialized. To fix a violation of this rule, pl
ease initialize non-global variables.

Cheers!

[RamblingCookieMonster]

Odd, getting an error trying to edit the issue. Was going to add that this could be added to @KirkMunro's issue #189.

Thanks!

[yutingc]

Thanks @RamblingCookieMonster for reporting the issue. I think we've fixed the issue for $PSBoundParameter but I'm not sure about $Matches. Regarding #189, we will need to have a discussion about this rule within the ScriptAnalyzer team to evaluate its usefulness as well as the noise it generates.
We will get back to you soon! Thanks for trying out PSScriptAnalyzer :-)

[RamblingCookieMonster]

Sounds good!

On a side note, spot checking other automatic variables from the following (incomplete) list, looks like it flags these as well.

[powershell]::Create().addscript({
    Get-Variable | Select -ExpandProperty Name
}).invoke()

Module version 1.0.1

Thanks!

Warren

[mwjcomputing]

I want to add that $PSVersionTable flags this warning as well.

[yutingc]

Thanks everyone. We will take a look at this bug.

[quoctruong]

Fixed with #241