Follow these steps to build a new package:
- See this tutorial to install vsce.
- Change the version number in
package.json. - At the root level, run the command:
vsce package
- A file named something like
vscode-todo-parser....vsixwill be generated. - Copy this file to built_packages folder.
Testing require a folder named "sample-code-file":
-
Contains sample files used to host random TODOs during testing.
-
At the beginning of each file, there must be 2 line specifying the commend rule of the language.
-
For example, a file named "sample.java" should start like this:
// /* */ static Main(String []args) { }
TravisCI is setup to build and run the test automatically for every pushes and merge requests.
It is integrated into Github directly, no need for external server.
Make sure that the environment contains this entry:
CODE_TESTS_WORKSPACE: ./test
For more details, read to this guide.
When ready to release a new version, do this:
- Update the changelog (CHANGELOG.md).
- Build a new package (see Build section above).
- Push branch
master. - Create a new release on Github.
- Update the extension on VSCode Marketplace.