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. Add Gitlab CI integration

    Sven Decabooter

    Problem/Motivation

    Steps to reproduce

    Proposed resolution

    Remaining tasks

    User interface changes

    API changes

    Data model changes

  2. Replace README.txt to README.md and update README.md

    Sven Decabooter

    The "configuration" section of the readme should describe that the Range Input widget needs to be selected for a relevant facet, and the Range Input processor be selected, for this to work.

    The help text in MR #5 does not correctly reflect this.

  3. Support OOP hooks

    Sven Decabooter

    Drupal 9 is no longer officially supported, and OOP hooks only work for 10.1+ anyway

  4. Support attribute-based plugins

    Sven Decabooter

    I could work on this if I find some time. Currently just reporting this, without intent to immediately provide some code.

  5. 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

  6. Support OOP hooks

    Sven Decabooter

    MR introduces PHPCS / PHPStan issues, which would ideally be resolved before merging.

  7. Fix PHPStan issues

    Sven Decabooter

    I think it would be better to ignore the PHPStan error about the internal class usage, by ignoring it through a phpstan.neon file in the project, rather than copying over the whole PHP class from core...

    Although just ignoring it might give a false sense of security, since we are overriding an internal class, that might suddenly break without BC warnings. But that should probably be covered by test scenario's.

  8. 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

  9. 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.

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.