feat: support globs in extends

[mrexox]

Closes #852

⚡ Summary

Support globs in extends option.

• Expand the possible globs before extending the main config
• Add tests

Probably need to change checksum check from the file checksum to a memory object checksum – #854

[VanTanev]

Hey, for some reason I didn't get a notification about your response in the discussion, sorry for getting back to you late!

This is a good step forward, but I think it needs one more improvement to be viable.

Configs that are extended should automatically set the commands.{}.root parameter to the folder of the extended config file.

Example, given:

# ./lefthook.yml
extends:
 - "apps/*/lefthook.yml"

and

# ./apps/store/lefthook.yml
pre-commit:
  commands:
    jest:
      run: pnpm jest --findRelatedTests --passWithNoTests {staged_files}

It will fail with:

ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "jest" not found

To fix it, one needs to manually add root: apps/store

# ./apps/store/lefthook.yml
pre-commit:
  commands:
    jest:
      root: apps/store # <!------ This needs to be added to every single command, even though it could be inferred from the file location.
      run: pnpm jest --findRelatedTests --passWithNoTests {staged_files}

Which is very clunky.

[mrexox]

Oh, I see. Yes, it might be too much to add root to every command, but now this is a must. I don't think it's a good idea to automatically add root because you can merge lots of files from different folders, and this can become too complicated to understand if something is added automatically.

Currently I don't have an elegant solution yet, so I have nothing to suggest except for explicit configuration for every command.

[VanTanev]

Yeah, the correct solution is not obvious. For example, lint-staged has the reverse approach, where leaf config files import from a root file, so it makes sense that commands are relative to leaf config file locations.

I do think that in the general case, automatically setting root for leafs should be fine, but there are definitely edge-cases, and such a change would be semver-breaking.

So, ultimately we're stuck with some repetition.