PowerShell / PowerShell/PSScriptAnalyzer
Add native command checking in UseCompatibleCommands
Open
Nobody has claimed this yet.
Area - Rules
Issue - Enhancement
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
UseCompatibleCommands already has information on what native commands are available in environments and where, and also comes with a platform-case-sensitivity-aware query API.
It would be reasonably straightforward to check for native command compatibility using this.
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 reading UseCompatibleCommands and its platform-case-sensitivity-aware query API to understand the available native-command data. Add native command compatibility checking so the analyzer can use that information; the work is done when incompatible native commands are detected using the existing availability and location data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100