Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Argument mode vs Expression mode

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
重构
描述清晰度
需要澄清
活跃度
停滞
技术栈
powershell
领域
tooling

调研方向

No files or tests are named. Start by reviewing the repository’s current syntax matches alongside PowerShell’s About Parsing reference and related issue #137. The work is done when argument mode and expression mode consistently scope operators, parameters, commands, and line continuations.

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

描述

For reference: Powershell Docs: About Parsing

The current syntax does not take in to account PowerShell's parsing, argument mode vs expression mode.

Lacking this is causing scoping of some operators when they should not be treated as such, and failure to scope operators when they should be treated as such, or properly scoping parameter tags vs commands that start with a '-', ect...

This actually would be a pretty large undertaking. It would probably go along with #137

This would probably require a reorganization of all the matches in to the repository, with the base match limited to just scanning the first token using a BEGIN with a forward lookup to sort out whether to run in expression or argument mode, ENDing at anywhere a line continuation isn't permitted, or otherwise at the end of a command (pipe, ';', etc) and this would require than any scoping that allows line continuation must also use BEGIN type matches to keep the parsing moving. The '&' could be a bit tricky, as it can be both the start of a command and the end of a command.

主要语言
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 摘要。