PowerShell / PowerShell/PSScriptAnalyzer
Which rules should provide suggested corrections?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
At present we have added the suggest correction property (see PR #508) to the following rules
PSAvoidUsingCmdletAliases
PSAvoidUsingPlainTextForPassword
PSMisleadingBacktick
PSUseToExportFieldsInManifest
PSMissingModuleManifestField (PR #515)
Which other rules should be equipped with this property so that it can improve authoring/editing PS scripts experience?
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 PR #508 and PR #515, then compare the listed rules: PSAvoidUsingCmdletAliases, PSAvoidUsingPlainTextForPassword, PSMisleadingBacktick, PSUseToExportFieldsInManifest, and PSMissingModuleManifestField. The issue is complete only when the applicable additional rules are identified and the scope for adding the suggested-correction property is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100