Warning about Hooks installation, when we use a custom autoloader

[llaville]

Note

This discussion is to alert Users that could run in trouble if you use a CaptainHook plugin that use a custom autoloader

Recently, I found issue with hooks installed that use my plugin https://github.com/llaville/captainhook-bin-plugin

I did not understood what was WRONG with git commit, because when I checked my hook with CaptN hook:pre-commit command, all was RIGHT !

Output

As the path to tools executable was not correct, I've though first that it came from my plugin, but this context was already fixed in version 1.0.2

So what are differences between live hook and CaptN hook checking command ?

I saw what are origin of this issue, when I look into hook installed

This hook was installed via Composer, with command :
vendor/bin/captainhook install --configuration=captainhook.json --only-enabled

For example : https://github.com/llaville/box-manifest/blob/4.3.0/composer.json#L63-L66

But my plugin use a custom autoloader (to check if tools are really installed or not), and not the default Composer Autoloader.

Important

This is my recommendation : check if your --bootstrap flag used the correct file

After reinstalling the hook with correct command: (if my use case, because I've a custom autoloader)
vendor/bin/captainhook install --configuration=captainhook.json --bootstrap=autoload.php --only-enabled

All run fine when applying live hook