This PR replaces the 'lowercase' option with a more generic 'transform' option that allows to supply a custom function that does key transforms. This is useful for models that respond to an item whose name is written in kebab-case (e.g. 'blog-article' or 'secondary-hero').

A PascalCase (Class name standard) to kebab-case (usually keys for Kirby items) transformer is included and added as default for models. Items previously using the 'lowercase' option have been replaced by the function.

This PR also updates a test (AmazeBlock -> VeryAmazeBlock) and adds a new page test (JustAnotherPage) to ensure the feature works.

related https://github.com/bnomei/autoloader-for-kirby/pull/2

i though again why excluded the file with additional dots by default. it had to do with a project where i replicated the k2 patterns plugin. that used a folder called patterns with snippets and snippetname.config.php file (like a controller for that pattern snippet). and i still like the idea that autoloader sticks to kirby defaults (like in their docs).

but since autoloader can be configured on creation you can easily make it load files with additions dots yourself using the ANY_ constants.

in you plugin index.php

autoloader(__DIR__, [
    'blueprints' => [
        'name' => \Bnomei\Autoloader::ANY_YML, // <-- this one is new and i will add it asap
    ],
    'snippets' => [
        'name' => \Bnomei\Autoloader::ANY_PHP,
    ],
]);

Currently, Autoloader can't load any model which counterpart has e.g. a hyphen in its name, which would be the case for kebab-case named models.

This might sound confusing, I'll explain it with an example: Lots of my blocks or pages end up with names like 'blog-article' or 'secondary-hero'. When specifying a model for such a type, the class needs to be specified in PascalCase, e.g. 'BlogArticlePage' or 'SecondaryHeroBlock'. Autoloader tries to resolve those cases to 'blogarticle' and 'secondaryhero', as it currently does not support kebab-case and only has an option for lowercase transforms.

A working code snippet for transforming would be $key = ltrim(strtolower(preg_replace('/[A-Z]([A-Z](?![a-z]))*/', '-$0', $key)), '-') (Adapted from StackOverflow).

Possible solutions for this is either adding support for specific transform cases yourself, which might be a lot of work or allowing a custom function to be set in the config that can be used to create such transforms yourself.

from @tobimori via discord

this is basically everything needed (i use the same finder component), you can optimise it for your code

    $finder = (new Finder())->files()
      ->name(static::PHP)
      ->in($dir);

    foreach ($finder as $file) {
      $pattern = strtolower($file->getRelativePathname());
      $pattern = preg_replace('~(.*)' . preg_quote('.php', '~') . '~', '$1' . '', $pattern, 1); // replace extension at end
      $pattern = preg_replace('~(.*)' . preg_quote('index', '~') . '~', '$1' . '', $pattern, 1); // replace index at end, for root of folder, but not in paths etc.

      $route = require $file->getRealPath();

      // check if return is actually an array (if additional stuff is specified, e.g. method or language) or returns a function
      if (is_array($route) || $route instanceof \Closure) {
        $this->registry[] = array_merge(
          [
            'pattern' => '/' . $pattern,
            'action' => $route instanceof \Closure ? $route : null
          ],
          is_array($route) ? $route : []
        );
      }
    }