PowerShell / PowerShell/PSScriptAnalyzer
Parallelize rules if possible
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Opening this generic issue while in a meeting with folks discussing PowerShell editor tooling.
@JamesWTruher believes that we are not parallelizing everything that we could be - the big one being rules execution. We should try to parallelize this as much as possible to get perf gains.
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
The issue names no file, test, or entry point; start by locating the rules-execution path in PSScriptAnalyzer and measuring its current performance. Determine which rule work can be parallelized safely, then verify the performance impact and analyzer behavior; done means the applicable rules execute in parallel with demonstrated gains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100