Een hart voor de Drupal Community

Bij make it fly geloven we sterk in Drupal en Open Source software in het algemeen. We maken dagelijks gebruik van vele open source componenten en de vele Drupal modules die beschikbaar zijn. We dragen actief ons steentje bij aan de community door zelf patches, modules en documentatie te voorzien, daarnaast zijn enkele teamleden ook actief in de Drupal User Group vzw.

Een overzicht van onze bijdragen aan de Drupal community vind je terug op onze Drupal.org pagina. Naast het actief meerwerken aan de Drupal community, zetten we ook andere ontwikkelaars op weg door vragen te beantwoorden op Drupal Answers.

  1. PHP error on the performance form screen

    Randal

    Hi @andybroomfield,

    Good catch! The class name was altered at the last moment before merge, seems I forgot to alter the service name. Thank you.

    I'll merge and release a new version.

  2. Support OOP hooks

    Randal

    Seems logical, I've added the hooks_converted parameter.

    Since the other threads are resolved, I'll merge into 1.2.x

  3. Support OOP hooks

    Sven Decabooter

    MR looks good to me. Maybe we also need to add the 'hooks_converted' parameter for performance improvement: https://www.drupal.org/node/3490771

  4. Support OOP hooks

    Sven Decabooter

    Seems like core is mostly putting all hooks together in a Hook\[MODULENAME]Hooks.php file, but I agree splitting up in logical chunks / files makes sense.

  5. Support OOP hooks

    Randal

    Processed the feedback.

    I was also debating whether the Help and Cron hooks could be merged into a "Core.php" file since they're both small hooks, but I just kept them in their own file. Figured it's better to keep things as split up as possible, which is the whole point of moving away from one gigantic .module file to OOP hooks :)

  6. Support OOP hooks

    Sven Decabooter

    - Hook help still needs to be added as OOP hook - All hooks need to be marked as converted, as per https://www.drupal.org/node/3490771

  7. Add Gitlab CI integration

    Sven Decabooter

    Problem/Motivation

    Steps to reproduce

    Proposed resolution

    Remaining tasks

    User interface changes

    API changes

    Data model changes

  8. Support attribute-based plugins

    Sven Decabooter

    Problem/Motivation

    Starting in Drupal 10.2.0, plugins should be defined with PHP attributes instead of annotations. When defining new plugin instances you should prefer PHP Attributes over annotations assuming the underlying plugin manager has been updated to support the use of attributes.

    Proposed resolution

    Allow PHP attributes for plugin definitions, as per https://www.drupal.org/docs/drupal-apis/plugin-api/attribute-based-plugins

  9. Support oop hooks

    Randal

    Problem/Motivation

    Implement OOP hooks for better OOP & DI support, instead of having all hook logic in the module file.

    Proposed resolution

    Convert hook implementations to OOP hooks, with backwards compatibility. See https://www.drupal.org/node/3442349

    Remaining tasks

    - Define hooks that can be converted into OOP hooks - Create hook clas(ses) to logically bundle relevant hooks with their logic - Add backwards compatibility support

    User interface changes

    N/A

    API changes

    N/A

    Data model changes

    N/A

  10. Support OOP hooks

    Randal

    @svendecabooter the changes have been applied in the MR. Feel free to check it out, everything seems to work fine.

    Changed minimum Drupal Core version to 10.1, PHP remains at >= 8.1.

  11. Add gitlab-ci file

    Bram Goffings

    Problem/Motivation

    Steps to reproduce

    Proposed resolution

    Remaining tasks

    User interface changes

    API changes

    Data model changes

  12. Abstract token usage

    Bram Goffings

    This merge request, together with https://www.drupal.org/project/ai_provider_openai/issues/3519302 Allowed me to create this module: https://www.drupal.org/project/ai_usage_limits

  13. AI usage limits

    Bram Goffings

    AI usage limits is a Drupal module that extends the Drupal AI module by allowing administrators to define usage limits for each enabled AI provider.

    Features

    Supports the following usage limits:

    • Input token usage
    • Output token usage
    • Total token usage
    • Cached token usage
    • Reasoning token usage

    Post-Installation

    Admin UI available at `/admin/config/ai/usage_limits`.

    Additional Requirements

    • Depends on the Drupal AI module.
    • Needs several patches to work at this moment
      • https://www.drupal.org/project/ai/issues/3517618
      • https://www.drupal.org/project/ai_provider_openai/issues/3519302
Sven Decabooter - Drupal Developer

"Onze teamleden bouwen zelf ook mee aan ons geliefde Drupal, en daar zijn we trots op"

Sven Decabooter
Drupal developer

Betrouwbare technologie, naadloze prestaties. Dat zijn onze Drupal-oplossingen.