PowerShell / PowerShell/PSScriptAnalyzer
Add rules for Named/Positional Parameter use on object creation
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
This PR in PowerShell - Add support for named argument with .NET Methods will add additional functionality which would be useful to add some rules around it's use to aid in coding styles, not only to aid in coding style but to reduce errors in use
Examples & levels that I think would be useful include
- Avoid mixing named & positional parameters on object creation (Information)
- Use only named parameters for object creation (Information)
- Use only positional parameters for object creation (Warning) (for backcompat checks
What is the latest version of PSScriptAnalyzer at the point of writing
1.22.0
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 reviewing the linked PowerShell PR for the named-argument behavior and clarify how PSScriptAnalyzer should distinguish object creation from other calls. Define the rule scope and severities for mixed, named-only, and positional-only parameters, then add analyzer coverage showing that each case produces the intended diagnostic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100