PowerShell / PowerShell/PSScriptAnalyzer
Add simple configuration for broad targets with compatibility rules
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Currently, the PSSA compatibility rules can only specify targets by name or path.
Compatibility target names are long, unintelligible and cumbersome.
Instead, users need to be able to do things like specify a list of PowerShell versions to target or a list of operating systems.
There needs to be a systematic, composable, human-readable way to specify these settings all the way from "everything" to "PowerShell 6.1 on Linux AND PowerShell 5.1 on Windows only".
While this resembles .NET RIDs, those form a simple lattice where the whole RID refers only to a granularity of operating system. A PowerShell platform can differ in operating system, PowerShell version, .NET version, .NET edition, machine architecture and process architecture (in decreasing order of importance).
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 files or tests; begin by locating the PSSA compatibility-rule handling for targets specified by name or path. Define how PowerShell versions, operating systems, and other platform dimensions should compose, then verify that the proposed configuration can express the stated broad and specific compatibility targets.
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
- 25/100