Before working on contributing files to GLS, file issue(s) regarding the changes you'd like to see.
The GLS language specification lives as a set of .md files under docs/Design.
Changes to the specification go through a three-step process:
- Document the specification changes
- Create BDD tests for the specification changes
- Implement the changes
These should all be done on a fork of the GLS repository, then sent as a GitHub pull request.
Each grouping of GLS commands has its own .md file.
Those files follow the format in docs/Design Doc Template.md.
Test files are located under test/integration and test/end-to-end. Tests are represented by a folder of files, where one file is GLS source code and each other file is how that code should look when compiled to each other language.
Follow the existing style guide for code. It helps to use the TSLint extension for your code editor.