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 摘要。