We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run Invoke-ScriptAnalyzer against the following with the new 1.19.1 release.
Invoke-ScriptAnalyzer
$foundFile = $false Get-ChildItem -Path . -File -Filter *.msi | ForEach-Object { $foundFile = $true } Write-Output "File found $foundFile"
No rule violations.
The variable 'foundFile' is assigned but never used. PSScriptAnalyzer(PSUseDeclaredVarsMoreThanAssignments) [3, 5]
If an unexpected error was thrown then please report the full error details using e.g. $error[0] | Select-Object *
$error[0] | Select-Object *
> $PSVersionTable Name Value ---- ----- PSVersion 5.1.18362.1474 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.18362.1474 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.19.1
The text was updated successfully, but these errors were encountered:
Duplicate of #1163
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce
Run
Invoke-ScriptAnalyzer
against the following with the new 1.19.1 release.Expected behavior
Actual behavior
If an unexpected error was thrown then please report the full error details using e.g.
$error[0] | Select-Object *
Environment data
The text was updated successfully, but these errors were encountered: