Thanks for your interest in improving vscode-vba!
Before you create a new issue, please first search in open issues to check it is not already reported.
In case your issue already exists, add a reaction and possibly create relevant comments.
Otherwise proceed with opening a new one.
Before making bigger changes, please discuss them in an issue.
In general PRs should be kept as small as possible (e.g. one feature/fix per PR). It allows merging them faster with less conflicts and will reduce review time.
- Create and clone a fork of https://github.com/serkonda7/vscode-vba
- Run
npm installinside the cloned directory - Create a new working branch for your changes
Every PR should contain a test case that covers the added feature or bug fix. This prevents regressions and makes reviewing the changes easier by proofing correct functionality.
Tests for the language grammar providing the syntax highlighting are in syntaxes/tests.
They can be run with the following command:
npm run test
If you'd like to install a development version of the extension, you can run the following:
npm run install-dev-extNote: you have to reload the VS Code window if open (run
>reload windowfrom command palette).
Currently there are no features that rely on typescript. Thus there is no need to compile or lint the code during development.