Author's note:
This extension is my way of giving back / saying thanks to the open-source community. If you are an open-source contributor then I take it as you already thanked. :)
Otherwise if you wanna express yourself you can buy me a coffee. Or you can just rate the extension. Whatever fits your budget.
- Report a bug ("properly").
- Tell me about your desired features.
- Create a pull request (against the development branch or master (if you sure your your PR is ready to be deployed)).
It is recommended to create a push hook:
cp ./resources/githooks/pre-push ./.git/hooks/pre-push
Content of .git/hooks/pre-push file:
#!/bin/sh
echo "pre-push hook:"
set -e -x
npm audit --production
npm run compile
npx mocha ./out/test/Documentation.test.js ./out/test/ESLint.test.jsnpm installAfter installing:
npm testAfter test:
- Open the folder in VSCode:
code .. - Let task
npm watchrun in the background. - VSCode "Run" / Debug page: Select
Manual cpp. - Start debugging.
- Add your folder to the newly opened VSCode's workspace. (Or change launch.json's
Manual cppto the folder which is intended to be debugged and the start.)
Issues are tipically related to file operations:
If you think your changes worth of a release add a new version entry to CHANGELOG.md file without a date. Travis will publish it automatically.
- doctest: supporting test suites
- Test cases: google test, catch2: info, warn, fail, stdout, stderr, capture, gtest_skip, gmock_verbose
- gaze is not good enough: detects change and delete, but not creation
- Use https://github.com/assistunion/xml-stream/blob/master/tests/test-readable-stream.js
- https://www.npmjs.com/package/ansi-colors
- https://code.visualstudio.com/api/working-with-extensions/publishing-extension
- https://matepek.visualstudio.com/_usersSettings/tokens
-
- run skipped directly; 2. run skipped by parent; see status: not resetted, shouldn't be
- merge changes from legacy
git difftool -d v3.6.31 v3.6.33 - if parallel exec limit > 1 then prefix PID