PowerShell / PowerShell/PSScriptAnalyzer
PSSCriptAnalyzer Needs Rule Sets
Open
Nobody has claimed this yet.
Area - Configuration
Area - Rule Sets
Issue - Enhancement
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
We need rule sets for minimum safety, basic design, recommended design, etc. When you start bringing in rules like mandating named parameters or placement of curly braces, you are way past the point where you should have started collecting them into sets.
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 how PSScriptAnalyzer currently registers and groups rules; the issue names no files, tests, or entry points. Done would mean agreeing on selectable rule sets such as minimum safety, basic design, and recommended design, then covering the grouping behavior with tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100