Repository navigation
Global variables are erroneously reported as "never used" #1300
Description
Activity
I agree with you that global variables should be included from the analysis as that's their nature and there is a separate rule that discourages them anyway, so I'd be happy to accept a PR with such a change
I have this issue as well. it seems that The analyzer should be aware of $Global:var as being in the host script outside the function as $var.
I agree with you that global variables should be included from the analysis as that's their nature and there is a separate rule that discourages them anyway, so I'd be happy to accept a PR with such a change
Global variables are discouraged? What should be used in place of them?
I was able to resolve my issues by setting my $global: to $script:
System Details Output
Issue Description
PowerShell extension reports global variables as assigned but not used when they are not used from within a
.psm1module file. However, global variables may be used by scripts outside that module importing it.Expected Behaviour
Global variables should never be reported as being unused.
Actual Behaviour
PowerShell extension reports global variables as assigned but not used when they are not used from within a
.psm1module file.