PowerShell / PowerShell/PSScriptAnalyzer
Accept `[ScriptBlock]` for `-ScriptDefinition`
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
[ScriptBlock]s might contain both single and double quotes therefore it would makes sense to accept a ScriptBlock for the -ScriptDefinition parameter so that it isn't necessarily to replace either the single quotes or double quotes in e.g. (Pester) test scenario's.
Proposed technical implementation details (optional)
Invoke-ScriptAnalyzer -ScriptDefinition { Write-Host 'Test:' "$Test" }
(Workaround)
Invoke-ScriptAnalyzer -ScriptDefinition { Write-Host 'Test:' "$Test" }.ToString()
What is the latest version of PSScriptAnalyzer at the point of writing
1.21.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 locating the parameter definition and handling for Invoke-ScriptAnalyzer's -ScriptDefinition option. Compare the existing string behavior with the proposed ScriptBlock example, then verify that quoted content is accepted without requiring ToString() while existing usage remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100