feature/lefthook

[interim17]

Problem

Closes #414 and #251

Solution

Installed lefthook and added config file with pre-commit checks for format, lint, typecheck, and testing.

We can adjust how strict we want pre-commit checks to be....

Some people find that lefthook doesn't play nice with the VSCode git GUI unless the window has been launched from the terminal, due to PATH variables being unavaiable (command npx not found, etc) I launched mine from terminal, and it worked fine.

With lefthook you may prefer committing from the CLI since the print out from lefthook is visible that way (tests running, etc). Without that readout it sometimes seems to be slow or just hanging if you commit from the VS code GUI.

We can go deeper on how to configure it: pre-commit vs pre-push or other options.

Advantages of lefthook over husky are that it can be used in polyglot projects although in this case we are just using it in node context.

• New feature (non-breaking change which adds functionality)

[Copilot]

Pull request overview

This PR adds lefthook as a Git hooks manager to enforce code quality checks before commits. The implementation runs format, lint, typecheck, and test commands automatically during the pre-commit phase.

Changes:

• Added lefthook as a dev dependency and configured it to install via the prepare npm script
• Created lefthook.yml configuration file with parallel pre-commit jobs for formatting, linting, type checking, and testing

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.

File	Description
package.json	Added lefthook dependency and prepare script to install Git hooks
lefthook.yml	Configured pre-commit hooks to run code quality checks in parallel

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The glob pattern in the lint script has a space before the file extensions which may not match files correctly. It should be \"src/**/*.{tsx,ts}\" without spaces around the comma.

[interim17]

it is defined

[Copilot]

The lint script in package.json uses its own glob pattern and doesn't accept file arguments. This will cause the staged_files parameter to be ignored. Consider updating the lint script to accept file arguments: eslint --quiet --fix

Suggested change

	run: yarn lint {staged_files}
	run: yarn lint

[rugeli]

I ran a bunch of experiments (switching commands with npx, adding fail_text as a job field, tweaking parameters etc. Here's update:

• for today's work, I wasn't able to fully fix vscode GUI popup readability issue. I did get the popup to show real text instead of empty lines, but it still feels a bit misleading.
• good news: the vscode Show Command Output view can be cleaned up using execution_info, this removes the extra blocks and special characters. Now the outputs looks much better.

these are the changes in this file that seemed useful during testing (I didn't submit a sub-pr since the changes are small and not yet optimal):

output:
    - summary
    - failure
    - execution_info
pre-commit:
    ...keep unchanged...

let me know what you think. I can work on this more and open a sub-pr if I find a better fix!