PowerShell / PowerShell/PSScriptAnalyzer
Necessary updates for the new ternary operator added in PowerShell language
Open
Nobody has claimed this yet.
Area - Engine
Issue - New Rule
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
The ternary operator will soon be added to the PowerShell language. Necessary updates may be needed for the PSSA:
- New AST type
TernaryExpressionAstis added. Changes are made to the visitors in PowerShell. The visitors in PSSA may need to be updated too.
/cc @rjmholt
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 PSSA visitors that correspond to PowerShell AST visitors, then review how PowerShell handles the new TernaryExpressionAst. Done means the relevant PSSA visitors support the ternary expression without breaking existing analysis; the payload names no specific files or tests.
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