Remove the cases specific to the crop_crop effect plugin and replace them with general management of effect plugins.

Created on 30 July 2024, 4 months ago
Updated 4 September 2024, 3 months ago

Problem/Motivation

In the CROP entity code, the use of the ‘crop_crop’ effect plugin is hard-coded at several key points in the process. Introducing complexity into the code, it takes the form of :

if(is_crop_crop) {
 do something
}
else {
 do something, but almost the same
}

The main problem this creates is that for retrieving the Crop Type in the ‘getCropFromImageStyleId’ method, only the ‘crop_crop’ plugin is allowed to have a selection of the Crop type, in all other cases the ‘Crop type’ must correspond to the Provider (the module) declaring the effect plugin.

Steps to reproduce

NA

Proposed resolution

It would be preferable to do away with these special cases and use the crop_crop plugin as the basis/template for implementing other CROP-based effect plugins.

Remaining tasks

Documentation :
- Specify that any effect plugin wishing to allow selection of the crop type must store this value in a storage named ‘crop_type’.

User interface changes

NA

API changes

All

Data model changes

NA

📌 Task
Status

RTBC

Version

2.0

Component

Code

Created by

🇫🇷France DrDam

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024