PowerShell / PowerShell/PSScriptAnalyzer
Add compatibility adapters
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
PSSA2 will change some APIs but should continue to provide a way for users depending on the current PowerShell API structure to continue using those to offer a migration path where possible.
This includes:
- Providing objects with the same properties and methods as today's output objects
- Supporting legacy parameters on commands
- Allowing old-style configuration when flags are passed otherwise configured
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 inventorying the current PowerShell API structure, including output objects, command parameters, and configuration flags, then compare it with the planned PSSA2 changes. Done means users can retain current objects and methods, use legacy command parameters, and use old-style configuration where possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100