PowerShell / PowerShell/PSScriptAnalyzer
Improve compatibility profile performance and make profiles a part of central configuration
Open
Nobody has claimed this yet.
Consider - 2.0
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Compatibility profiles are currently very slow to start up and use opaque and duplicated configurations across rules.
Instead:
- They should be more modular so they can be more easily read in
- They should ideally have a custom parser for speed
- Rather than being configured by name, they should be specified by PS and OS version and defaults should be implicitly listed in each PSSA version
- Profiles should be lazily taken from NuGet rather than distributed with PSSA
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 compatibility-profile loading and central configuration paths, then trace how profiles are read during startup. Compare the current named-profile behavior with the requested PowerShell and OS version selection, implicit defaults, custom parsing, and lazy NuGet retrieval. Done means these requirements are implemented without the current duplicated configuration and startup slowdown.
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