PowerShell / PowerShell/vscode-powershell
Semantic Syntax is incorrectly highlighting arguments as commands
Open
Nobody has claimed this yet.
Area-Semantic Highlighting
Issue-Bug
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Any bare (unquoted) string argument that has a - in it is being highlighted as a command:
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
Reproduce the example in VS Code with a bare, unquoted argument containing a hyphen, then trace the TypeScript semantic-syntax highlighting path; the issue names no file or test. Done means such arguments are highlighted as arguments rather than commands, without regressing command highlighting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100