PowerShell / PowerShell/PSScriptAnalyzer
Enable composition of profiles (like to add large module libraries, e.g. Az)
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
Allow the breaking out of compatibility profile components into pieces so that they can be composed at rule-execution time.
Ideally this would mean a new field on compatibility rules of some kind to tack on a profile to another profile. For cmdlet-based profile manipulation, this might look like Join-PSCompatibilityProfile.
This is mainly me recording this thought for later
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 examining compatibility profile components, compatibility rules, and the rule-execution path. The issue suggests either a composable profile field or a Join-PSCompatibilityProfile cmdlet, but it does not identify files, tests, or a settled design; done would mean composing profile pieces for large module libraries such as Az.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100