You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tmLanguage XML files are converted from their YAML-tmLanguage source files like this:
npx lix run vshaxe-build --target tm-language-conversion
Tests
There are some automated tests that can be run like this:
npx lix run vshaxe-build --target tm-language-tests
/cases contains the actual test cases. When running build.js, scope-annotated files are generated into the /generated directory. During the test step (running test.js), the files in /baselines are compared with the newly /generated ones, and the test fails if they are different.
So when adding a new test, follow these steps:
create a new test case in /cases
verify that the highlighting is ok
run build.js and copy the new file in /generated into /baselines
Workflow
For convenience, there exists a tm-language target, which runs both the tm-language-conversion and tm-language-tests targets. If you have this project open in VSCode, you can just execute the build task (Ctrl+Shift+B) to run the tm-language target.
VSCode currently needs to be restarted to pick up changes to grammar files. Hence it is helpful to assign an easily accessible shortcut to the Reload Window command, for instance F6. Sublime Text's PackageDev extension may offer a better workflow in this regard.
VSCode has a "Developer: Inspect Editor Tokens and Scopes" command that can be very helpful.