Improved hook injection logics and the default hooks

[Davidyz]

#200

Fix #201

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.49%. Comparing base (b70ded9) to head (c4bd65f).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #202   +/-   ##
=======================================
  Coverage   99.49%   99.49%           
=======================================
  Files          21       21           
  Lines        1589     1589           
=======================================
  Hits         1581     1581           
  Misses          8        8           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Davidyz]

@deas I've implemented the changes to the hooks that you proposed in #200 (in slightly different ways bc your snippet didn't quite work). It'll also throw warnings on hooks that are symlinked. Could you give this a try?

[deas]

@deas I've implemented the changes to the hooks that you proposed in #200 (in slightly different ways bc your snippet didn't quite work). It'll also throw warnings on hooks that are symlinked. Could you give this a try?

What was the part that did not work for you?

[deas]

Oops, already on main. Don't know how and when you release from main, so this ships via lazy.nvim. Guess I should learn a bit about the toolchain (never heard of pdm), so I can run and try vectorcode straight from a source folder.

[Davidyz]

Oops, already on main. Don't know how and when you release from main, so this ships via lazy.nvim. Guess I should learn a bit about the toolchain (never heard of pdm), so I can run and try vectorcode straight from a source folder.

You don't need pdm to build from source. Pdm is only for development. Both uv tool and pipx support installing from a git URL or a local dir. As for the release, I just tag a commit with the version number, and a GitHub action workflow will take care of the rest. I think we're pretty close to the release. I plan to test with some more models and see how they work with the new tool schema, and if everything turns out okay, I'll make the release (hopefully no later than this weekend). This is not a core functionality so I'm not too concerned about it for this release. 0.7.0 is really more about giving LLMs the ability to vectorise things.

[deas]

I think we should document the ideas behind the hooks in general and also drop some comments in the fragments. It is just a few lines shell script - still anything but self explanatory. ;)

[Davidyz]

we should document the ideas behind the hooks in general and also drop some comments in the fragments.

I'll do a full review of the readme/documentation before the 0.7 release (it's been a while since the last time I did this) and make changes where necessary. I'll briefly explain what the default hooks do in the changes. As for a detailed explanation on what each part of the shell script does, CodeCompanion+VectorCode did an exceptional job at locating the relevant code and explaining the hooks, so I'd say we're good.