PowerShell / PowerShell/PSScriptAnalyzer
New Rule Request : Use double quoted strings when using variable expansion
Open
Nobody has claimed this yet.
Issue - New Rule
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
It is a common mistake to use single quotes for a string with a variable like this:
Write-Verbose 'My value is $someValue';
It would be nice if this could be detected (as a warning?)
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 tracing how PSScriptAnalyzer implements existing rules and how their tests report warnings for PowerShell string literals. Use the example in the issue to define the detection case, then check related rule tests and confirm the warning behavior and false-positive boundaries before considering the work done.
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
- Mostly clear
- Newbie friendliness
- 35/100