Asterisk is not recognized as valid function/cmdlet name character

未关闭
#200 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
powershell
领域
devtools

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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:
grafik
In PowerShell itself:
grafik

Calling such a function/cmdlet...

In VSCode:
grafik
In PowerShell itself:
grafik

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

grafik

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)

主要语言
PowerShell
星标
151
派生
55
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

PowerShell/EditorSyntax 的其他 Issue

查看 PowerShell/EditorSyntax 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。