| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
Updated documentation for environment setup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixed Mocha tests + added debugging configurations to vscode
|
|
|
|
- Preventing mocha timeouts due to hitting breakpoints
|
|
|
|
|
|
|
|
- Added a new esbuild for:
- bundling test runners (run tests on vscode + mocha runner)
- bundling all tests in the project
- Some opinionated renamings / moving test related things around
- Changed output directory in tsconfig to avoid overriding the entire out directory - bundles tests also go there
Some poking around trying to deprecate jest as it is not used and mocha is more often used for vscode extension testing.
Though I assume jest was added to test GUI within extension.
This work was started because there are compilation issues with the current setup and neither of the tests are actually working so figured getting one to a working spot is a good start
|
|
|
|
Improved 2 click setup experience for new devs
|
|
|
|
|
|
|
|
Added example directory with a typescript program and open it by default in the extension host - its nice to have an isolated environment where the extension can be played with. You can always open an actual project folder if you want to
|
|
|
|
|
|
|
