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
Line numbers are missing for the Rule "Missing Line Number for PSUseBOMForUnicodeEncodedFile"
Introduce a file test.ps1 with the following content:
Get–ChildItem
Run the PSScriptAnalyzer in the directory where the file remains.
Be aware of the dash:
The character U+2013 "–" could be confused with the character U+002d "-", which is more common in source code.
Invoke-ScriptAnalyzer -Recurse -Path . RuleName Severity ScriptName Line Message -------- -------- ---------- ---- ------- PSUseBOMForUnicodeEncodedFile Warning test.ps1 1 Missing BOM encoding for non-ASCII encoded file 'test.ps1'
Invoke-ScriptAnalyzer -Recurse -Path . RuleName Severity ScriptName Line Message -------- -------- ---------- ---- ------- PSUseBOMForUnicodeEncodedFile Warning test.ps1 Missing BOM encoding for non-ASCII encoded file 'test.ps1'
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 7.2.5 PSEdition Core GitCommitId 7.2.5 OS Microsoft Windows 10.0.19044 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0 > (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() } 1.21.0
The text was updated successfully, but these errors were encountered:
this would be nice
Sorry, something went wrong.
No branches or pull requests
Line numbers are missing for the Rule "Missing Line Number for PSUseBOMForUnicodeEncodedFile"
Steps to reproduce
Introduce a file test.ps1 with the following content:
Run the PSScriptAnalyzer in the directory where the file remains.
Be aware of the dash:
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: