Een hart voor de Drupal Community

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

Gave some feedback on the MR

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.

Randal added a comment on drupal.org: Support oop hooks

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

randalv created an issue. See original summary.

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

randalv made their first commit to this issue’s fork.

I created a dev release

Bram Goffings added a comment on drupal.org: Add gitlab-ci file

Bram Goffings added a comment on drupal.org: Abstract token usage

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

aspilicious created an issue. See original summary.

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

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 added a comment on drupal.org: Add schema validation

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

svendecabooter created an issue. See original summary.

Sven Decabooter added a comment on drupal.org: Automated Drupal 11 compatibility fixes for entity_logger

Thanks for the review. Hopefully this can be merged in quickly, to unblock multilingual sites from using la_eu.

Sven Decabooter added a comment on drupal.org: Automated Drupal 11 compatibility fixes for facets_range_input

Sven Decabooter added a comment on drupal.org: Automated Drupal 11 compatibility fixes for facets_range_input

svendecabooter made their first commit to this issue’s fork.

Thanks for the patch. It doesn't look like UUID export will be committed to core anytime soon, but in the meantime we can already add support for people using this patches in the referenced issue.

svendecabooter credited harrrrrrr.

Sven Decabooter added a comment on drupal.org: Support block_uuid inline block configuration

D11 support is in the 3.x branch. Closing this issue.

svendecabooter credited harrrrrrr.

Thanks for the report and fix. We had encountered the same issue in one of our projects, and confirmed this as a solution.

Sven Decabooter added a comment on drupal.org: Automated Drupal 11 compatibility fixes for contextual_image_widget_crop