PowerShell / PowerShell/PSScriptAnalyzer
Update PSUseCorrectCasing to enforce correct casing of language keywords
Open
Nobody has claimed this yet.
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 language keywords should result in a PSUseCorrectCasing rule violation.
A list of keywords can be obtained by reflection:
[ref].Assembly.GetType('System.Management.Automation.Language.Tokenizer').
GetDeclaredField('_keywordText').
ForEach{ $PSItem.GetValue($null) }
elseif
if
else
switch
foreach
from
in
for
while
until
do
try
catch
finally
trap
data
return
continue
break
exit
throw
begin
process
end
dynamicparam
function
filter
param
class
define
var
using
workflow
parallel
sequence
inlinescript
configuration
public
private
static
interface
enum
namespace
module
type
assembly
command
hidden
base
What is the latest version of PSScriptAnalyzer at the point of writing
1.19.0
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 with the PSUseCorrectCasing rule and the PowerShell keyword list obtained through Tokenizer reflection. Check how the rule currently detects casing violations, then cover the listed keywords and verify that incorrectly cased language keywords are reported while correctly cased ones are accepted.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100