PowerShell / PowerShell/PSScriptAnalyzer
Parameters that accept wildcards do not have the SupportsWildcards attribute
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
The following cmdlets have the listed parameters that support wildcards. However, those parameters to do have the [SupportsWildcards()] attribute. This makes discovery of wildcard support impossible. PlatyPS cannot create accurate documentation.
Get-ScriptAnalyzerRule
- CustomRulePath
- Name
Invoke-ScriptAnalyzer
- CustomRulePath
- ExcludeRule
- IncludeRule
- Path
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
Locate the parameter declarations for Get-ScriptAnalyzerRule and Invoke-ScriptAnalyzer, then inspect how PlatyPS discovers wildcard support. Verify the listed parameters and confirm that generated documentation exposes their wildcard capability. Done means all listed parameters are represented accurately for wildcard discovery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- documentation, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100