Ability to bind concerned PowerShell version to a rule
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the AvoidUsingWMICmdlet rule documentation and the linked UseCompatibleStrings, UseCompatibleSyntax, and AvoidNewObjectCmdlet issues. Then trace how rules are represented and how #Requires -Version is handled. Done means the proposed minimum-version behavior, suppression, and UseRequiresStatement behavior have a defined implementation scope.
Written by the indexing model from the issue text.
Description
It might be helpful that in the case a rule only applies to a specific (minimum) PowerShell versions as for e.g.:
And new request/issues:
to have the possibility to add that (minimum) PowerShell version (e.g. MininumPowerShellVersion) to that rule.
Meaning e.g. the AvoidUsingWMICmdlet rule might have MininumPowerShellVersion set to 3.0
This would add the possibility for two additional features:
- Suppressing the specific rule by using the
#Requires -Version x.xstatement.
E.g.:- adding
#Requires -Version 2.0would suppress theAvoidUsingWMICmdletrule - adding
#Requires -Version 7.0would allow the use of`e(suppress the proposedUseCompatibleStringsrule)
- adding
- A general
UseRequiresStatementrule when a rule with a minimal version applies and the#Requires -Version x.xis not set (or set incorrectly)
E.g. if any of the rules applies, it generate a warning that the#Requires -Version x.xstatement should be set.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 415
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
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.
More from PowerShell/PSScriptAnalyzer
-
Up-for-Grabs
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSScriptAnalyzer#2213 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
PowerShell/PSScriptAnalyzer#2217 · 1 comment ·
-
PSUseConsistentIndentation double-indents attribute bodies that open a scriptblock (`[Attr({ … })]`) Open
Difficulty 3/5 1-2 days Newbie friendliness 70/100
PowerShell/PSScriptAnalyzer#2216 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
PowerShell/PSScriptAnalyzer#2211 ·
-
`PSPlaceOpenBrace` and `PSPlaceCloseBrace` leave trailing whitespace when expanding one-line blocks Open
Difficulty 3/5 1-2 days Newbie friendliness 70/100
PowerShell/PSScriptAnalyzer#2210 ·
All issues in PowerShell/PSScriptAnalyzer
Similar issues
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·
-
Issue-Enhancement Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 2 reactions ·
-
dependencies needs-team-triage server-Azure.Mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
aspnet-core/svc aspnetcore-signalr/subsvc doc-enhancement Pri2 SignalR
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/AspNetCore.Docs#37729 ·