Schema missing for "focal_point_crop_by_width" effect

Thanks for the report and the patch @detroz, this is spot on.

I hit the same validation error using focal_point_crop_by_width in a recipe, and it's exactly what you found: there's no config schema entry for the effect, so width, height and crop_type all get flagged as unknown keys.

I've moved your fix into an MR (!59) so it can run through the current CI, and added a small kernel test so this doesn't quietly regress. The test builds an image style with the effect and checks the config validates against schema, it fails on the current code and passes once the schema is added.

Pipeline passes with warnings. phpunit is green. The cspell/eslint/phpcs/phpstan/stylelint warnings are already there on 2.x and none of them touch the files in this change.

Environment

• Drupal: 11.4.4
• PHP: 8.5.5
• Database: MariaDB 10.11.16
• DDEV: v1.25.2
• Focal Point: 2.1.2

Prerequisites

• Focal Point module enabled.
• The focal_point_crop_by_width image effect is used in an image style (as happens when installing a recipe or importing config that defines it). Strict config schema validation runs on recipe install and config import.

Steps

1. Apply the fix from MR !59: add the image.effect.focal_point_crop_by_width entry to config/schema/focal_point.schema.yml.
2. Rebuild caches: ddev drush cr
3. Create an image style that uses the focal_point_crop_by_width effect and validate its config against the schema:
   

   ddev drush php:eval '$s=\Drupal::entityTypeManager()->getStorage("image_style")->create(["name"=>"tester_fp","label"=>"Tester FP"]); $s->addImageEffect(["id"=>"focal_point_crop_by_width","weight"=>0,"data"=>["width"=>300,"height"=>200,"crop_type"=>"focal_point"]]); $s->save(); $c=\Drupal::config("image.style.tester_fp")->get(); foreach(\Drupal::service("config.typed")->createFromNameAndData("image.style.tester_fp",$c)->validate() as $v){print $v->getPropertyPath().": ".strip_tags((string)$v->getMessage())."\n";}'

4. Compare the validation output before and after the fix.

Expected results

• The config for an image style using the focal_point_crop_by_width effect validates cleanly against the schema.
• No "unknown key" violations for width, height, or crop_type.
• Recipes and config imports that define this effect install without validation errors.

Actual results

Before the fix, validating an image style that uses the focal_point_crop_by_width effect reports three "unknown key" violations — 'width', 'height', and 'crop_type' are all flagged because no config schema exists for the effect, which breaks recipe installation and config import. After adding the missing image.effect.focal_point_crop_by_width schema entry, validation returns zero violations and the effect config is accepted.

Testing produced with the assistance of an LLM.

Updating version to patch against

MR Merged!