PowerShell / PowerShell/PSScriptAnalyzer
Update PSUseCorrectCasing to enforce correct casing of automatic variables
Open
Nobody has claimed this yet.
Area - Rules
Issue - Enhancement
Up-for-Grabs
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Summary of the new feature
Incorrect case of automatic variables should result in a PSUseCorrectCasing rule violation.
Proposed technical implementation details (optional)
Code using $error should result in a rule violation
Replacement with $Error should be suggested as a fix.
What is the latest version of PSScriptAnalyzer at the point of writing
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
Start by locating the PSUseCorrectCasing rule and its handling of automatic variables. Reproduce the $error case, then verify that incorrect casing is reported and a $Error replacement is suggested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100