PowerShell grammar categorizing member values differently.

未关闭
#160 15 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

Compare the older and newer PowerShell grammar classifications for the reported Name member, using the VS Code no-extension reproduction described in the issue. Check the related comment discussion for an agreed intended scope, then confirm whether the grammar or theme behavior should change and verify the resulting classification in VS Code.

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

描述

From @cblackuk on February 18, 2019 10:16

  • VSCode Version: >1.27.2
  • OS Version: Win10, 2016, 2019 - does not matter

Steps to Reproduce:

On VSC with no extensions 1.27.2, using an older version of the PowerShell grammar Name is classified as entity.name.function.invocation.powershell.
image

On VSC with no extensions >1.27.2, using a more recent version of the PowerShell grammar Name is classified as variable.other.member.powershell
image

Was this change intentional? It changes the way the code looks in VS Code since the built in themes don't use variable.other.memeber

Copied from original issue: Microsoft/vscode#68910

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

贡献指南

打开贡献指南

从这里开始

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

PowerShell/EditorSyntax 的其他 Issue

查看 PowerShell/EditorSyntax 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

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