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.
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 :)
- 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
See https://www.drupal.org/node/3490771
svendecabooter created an issue. See original summary.
Reverted, because module still contains a preprocess procedural hook.
See https://www.drupal.org/node/3490771
svendecabooter created an issue. See original summary.
See https://www.drupal.org/node/3490771
svendecabooter created an issue. See original summary.
Thanks for the MR and improvements!
svendecabooter created an issue. See original summary.
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.
svendecabooter changed the visibility of the branch 3337791-replace-readme.txt-to to hidden.
Thanks for the MR. Committed now.
Drupal 9 is no longer officially supported, and OOP hooks only work for 10.1+ anyway
I could work on this if I find some time. Currently just reporting this, without intent to immediately provide some code.
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.
Allow PHP attributes for plugin definitions, as per https://www.drupal.org/docs/drupal-apis/plugin-api/attribute-based-plugins
svendecabooter created an issue. See original summary.
"Onze teamleden bouwen zelf ook mee aan ons geliefde Drupal, en daar zijn we trots op"