* migrate chatButtonClicked
* changeset
* send targeted event to the controller
* prettier
* add test mock
* continue to fix tests
* fix test mocks once and for all
* fix test mocks once and for all
* try again please lord
* try again
* temporarily disable tests
* revert other test 'fixes'
* one more
---------
Co-authored-by: Elephant Lumps <celestial_vault@Elephants-MacBook-Pro.local>
* add a matrix strategy for testing
* Handle EOL on Windows
* use bash as shell on every os and run the test-ci script
* fix tsconfig path resolution using the __dirnname
* print test results regardless of status
* Limit artifact upload to Linux
* update the test-cli
* Add windows-specific dependencies as optional dependencies
lightningcss-win32-x64-msvc
rollup-win32-x64-msvc
* Do not collect coverage on Windows
* Use UTF-8 on the Python Scripts
* force the ubuntu-latest name to be `test`
* Run pretest in CI to build all tests
* Alias paths when running tests
* Bundle ES modules with esbuild
* alias packages
* Preserve the test scripts exit code and display the output
* Remove outdated test
* Fix: Better Windows path support
* Move to 'chai' for test running
* Fix: Let's start with what we know
* Chore: Add 'root' level file path test, remove less useful tests
* Chore: Add 'root' level file path test, remove less useful tests
---------
Co-authored-by: Dennis Bartlett <bartlett.dc.1@gmail.com>
* add coverage to github workflows
* add changeset
* continue to run on errors
* address comments from ellipsis-dev
* add unit tests, confirm passing
* remove pyproject.toml approach to deps instalL
* use github_output env var
* add verbose mode for debugging
* verbose was not being captured
* std out, not print
* remove 1000 line dump...
* print every line separately to prevent clipping
* build extension before testing
* clean up debugging prints
* break coverage.py into smaller files
* break coverage.py into smaller files
* Relative module names not supported
* rename coverage to coverage_check to avoid naming collision
* rename coverage to coverage_check to avoid naming collision
* debugging missing coverage files
* output error on coverage report
* handling ellipsis-dev comments
* see if we need vscode test deps
* experimenting to try to get it running
* use absolute paths
* put everything in root directory
* address more comments from ellipsis-dev
* import run_command in extraction.py
* fix verbose flag
* use parent parser
* ensure safe command test will allow our commands
* make sure we install before coverage
* update tests to ensure run
---------
Co-authored-by: Dennis Bartlett <bartlett.dc.1@gmail.com>
