PowerShell / PowerShell/PSScriptAnalyzer
PowerShellVersion should be required for modules
Open
Nobody has claimed this yet.
Issue - New Rule
Up-for-Grabs
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Users need to know the PS version requirements for a module. To specify, add a value for PowerShellVersion key in the module manifest.
To verify, get the manifest:
iex (cat -raw (gmo -list ).Path)
Or PSModuleInfo
(gmo -list ).PowerShellVersion
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 module manifests are inspected and how PowerShellVersion is exposed through PSModuleInfo. Use the manifest and PSModuleInfo commands in the issue to reproduce the current behavior. Done means modules declare a PowerShellVersion value and the requirement can be verified through both listed checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100