PowerShell / PowerShell/PSScriptAnalyzer
possible bug with PSUseBOMForUnicodeEncodedFile
Open
Nobody has claimed this yet.
Area - Rules
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Second version of this causes BOM to be considered missing, No failed test after deleting trailing whitespaces after Property. Not sure if false positive or personal mistake, worked fine with and without -Typename as well.
$MovedUser = New-Object PSObject -Property @{...}
$MovedUser = New-Object -TypeName PSObject –Property @{...}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the PSUseBOMForUnicodeEncodedFile behavior with the two New-Object snippets, both with and without -TypeName, and after removing trailing whitespace. Determine whether the BOM warning is a false positive or a usage mistake, then capture a confirmed failing case and its expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100