Missing line number in rule PSUseBOMForUnicodeEncodedFile

Line numbers are missing for the Rule "Missing Line Number for PSUseBOMForUnicodeEncodedFile"

Steps to reproduce

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.

Expected behavior

Invoke-ScriptAnalyzer -Recurse -Path .

RuleName                            Severity     ScriptName Line  Message
--------                            --------     ---------- ----  -------
PSUseBOMForUnicodeEncodedFile       Warning      test.ps1   1     Missing BOM encoding for non-ASCII encoded file 'test.ps1'

Actual behavior

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 *

Environment data

> $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

提供された test.ps1 の内容と Invoke-ScriptAnalyzer コマンドを使って問題を再現し、その後、リポジトリで PSUseBOMForUnicodeEncodedFile と診断の作成箇所を検索します。test.ps1 に対して警告が 1 行目を報告し、非 ASCII ファイルのケースをカバーする回帰テストがあれば完了です。