This project establishes the central development and maintenance of syntax definition files for the PowerShell language used by editors that leverage the XML version of the TextMate language grammar format.

Currently this syntax definition is used in the following editors and extensions:

• Visual Studio Code by Microsoft
• PowerShell Package for Sublime Text by Guillermo López-Anglada
• language-powershell for Atom by James Sconfitto

In the future we may find a more common syntax that allows us to generate syntax definitions for editors that don't leverage the TextMate format.

We are starting with the current state of the TextMate grammar that is being used in both VS Code and Sublime Text. There are a number of existing issues with the grammar that we need to track down and fix. Please see issue #1 for more details.

• Node.JS, >= 8.9.1
• Atom text editor (tests)

1. Run build.ps1 to generate the grammar.

   PS> .\build.ps1
   

2. The .json file will be generated in ./grammars/ at the root of the project.

Requires the Atom text editor be installed.

1. Run .\build.ps1 with -Test. Which will build the grammar file and run all of the specs.

   PS> .\build.ps1 -Test
   

1. Use npm to install dependencies:

   npm install
   

2. Run the build-grammar script to generate the json file.

   npm run build-grammar
   

3. The .json file will be generated in ./grammars/ at the root of the project.

1. Build the grammar file using the above steps.

2. Use the Atom cli command for your os (atom.cmd or atom.sh) to run the tests from the root of the EditorSystax project folder.

   atom --test spec
   

We would love to have community contributions to this project to make PowerShell syntax highlighting great in as many editors as we can. Please feel free to file issues or send pull requests if you'd like to contribute.

• Andy Jordan
• Nick James

This extension is licensed under the MIT License. Please see the third-party notices file for details on the original source of the TextMate definition that we use.

Please see our Code of Conduct before participating in this project.

For any security issues, please see our Security Policy.