Asterisk is not recognized as valid function/cmdlet name character
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- devtools
Research direction
Start with the PowerShell examples function Get-A*A {} and Get-A*A, then inspect the syntax-highlighting rules and autocomplete behavior for function and cmdlet names. Reproduce the issue in VS Code and compare it with PowerShell itself and GitHub highlighting; done means the asterisk remains part of the name, uses the same color, and does not trigger an incorrect suggestion.
Written by the indexing model from the issue text.
Description
Environment
- Editor and Version VS Code
- Your primary theme: High Contrast Default
Issue Description
The character * is not recognized as part of a function/cmdlet name
Screenshots
Defining such a function...
In VSCode:

In PowerShell itself:

Calling such a function/cmdlet...
In VSCode:

In PowerShell itself:

To show that the semantics are wrong, too, here's an autocomplete popup:

Expected Behavior
The asterisk and the rest of the function name should be the same color and the asterisk should not interrupt the function name and cause suggestions to pop up all of a sudden.
Code Samples
function Get-A*A {}
Get-A*A
(GitHub highlighting is also wrong, here)
- Dominant language
- PowerShell
- Stars
- 151
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
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.
More from PowerShell/EditorSyntax
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
PowerShell/EditorSyntax#224 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
PowerShell/EditorSyntax#222 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
PowerShell/EditorSyntax#221 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PowerShell/EditorSyntax#220 · 2 comments · 1 reaction ·
-
Issue-Bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
PowerShell/EditorSyntax#219 · 2 comments ·
All issues in PowerShell/EditorSyntax
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
newrelic-experimental/preflight#793 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
caddyserver/caddy#8046 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zilliztech/memsearch#759 ·
-
comp/cron P2 sweeper:risk-automation type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#117792 · 1 comment ·