Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Question: Interest in replacing build-grammar.js with a purely PowerShell solution?

未關閉
#159 3 則留言 3 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
javascript, powershell
領域
build-system, tooling

研究方向

Start by comparing tools/build-grammar.js with the referenced build_grammar.ps1 and the PwshReadXmlPList implementation. Check whether their generated JSON and PowerShell version requirements match the existing build behavior. The issue is a proposal, so completion criteria and maintainer direction are not established.

由索引模型根據 Issue 內容生成。

描述

Would there be any interest in replacing the build-grammar.js script (in tools) with a purely PowerShell based solution? I have created a script/function/class that provides the equivalent of 'fast-plist' using the .NET XML reader and a PowerShell script (using a class) to 'ConvertFrom-Plist'.

Two caveats.

  1. For performance reasons, I used a class, due to the fact that the inner function is highly recursive. The class with static method improved performance in excess of 4:1. This limits to PowerShell 5.0+.
  2. In order to as closely match the formatting of the existing JSON file output, PowerShell 6.0+ is required, and a -replace operation to replace the space indent with tabs.

Reference:
https://github.com/msftrncs/PwshReadXmlPList

https://github.com/msftrncs/EditorSyntax/blob/build_grammar.ps1/tools/build-grammar.ps1

主要語言
PowerShell
星號
151
分支
55
30 天內沒有已合併 PR

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

PowerShell/EditorSyntax 的其他 Issue

查看 PowerShell/EditorSyntax 的全部 Issue

相似的 Issue

更多 Build System Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。