Currently we just launch the TUI when the user invokes the program, but going forward we will also want to be able to do other things for which we will need other commands. I've used the click package to allow for adding other commands and I've added one to get us started (tui).
Type of change
[ ] Documentation (non-breaking change that adds or improves the documentation)
[x] New feature (non-breaking change which adds functionality)
[ ] Optimization (non-breaking, back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (whatever its nature)
Key checklist
[x] All tests pass (eg. python -m pytest)
[ ] The documentation builds and looks OK (eg. python -m sphinx -b html docs docs/build)
[x] Pre-commit hooks run successfully (eg. pre-commit run --all-files)
Further checks
[x] Code is commented, particularly in hard-to-understand areas
[ ] Tests added or an issue has been opened to tackle that in the future. (Indicate issue here: # (issue))
Description
Currently we just launch the TUI when the user invokes the program, but going forward we will also want to be able to do other things for which we will need other commands. I've used the
clickpackage to allow for adding other commands and I've added one to get us started (tui).Type of change
Key checklist
python -m pytest)python -m sphinx -b html docs docs/build)pre-commit run --all-files)Further checks