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

Offen

#159 erstellt am 15.2.2019 3 Kommentare 3 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit: 5/5
Geschätzter Aufwand: Über eine Woche
Anfängerfreundlichkeit: 25/100

Issue-Typ: Feature
Klarheit: Muss geklärt werden
Aktivitätsstatus: Veraltet
Tech-Stack: javascript, powershell
Bereich: build-system, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

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+.
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