PowerShell / PowerShell/PSScriptAnalyzer
Start using PowerShell Standard 3
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Summary of the new feature
Use PSStandard to simplify PowerShell references and potentially reduce the amount of binaries to ship. Because 1 rule is not available for ps v3 and v4, it might only be possible to use it for the engine project for starters. We need to explore and take it from there.
What is the latest version of PSScriptAnalyzer at the point of writing
1.17.1
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
Begin by locating the engine project and its existing PowerShell references, then verify what PSStandard 1.17.1 supports for PowerShell 3 and 4. Done means a decided scope for adoption, including whether an engine-only start is viable and its binary impact; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100