[2.7.1] Why separate package and failure on composer-require-checker about cloudinary_php HOT 1 CLOSED

@ruudk , thank you for your feedback!

We have extracted transformations to a separate package since we will release a few more packages that will depend on it soon.

Regarding PHP version... Yeah, that is a good point. Since this is an SDK and many products/integrations/frameworks use it, we don't want to limit them to the old versions of the SDK, or restrict them, and force them to bump their versions, unless it's absolutely nessesary. If you check packagist, there are many libraries who still have minimum PHP version 5.6.

And it's not that we are in desperate need of the latest PHP features. We will do it at some point for sure. And the code perfectly works with all the versions, including 8.1.

PSR-4. Yeah, we have two main goals here: Provide discoverability for users, while keeping the code base well structured.

Not all of our users use smart IDEs, some use simpler editors, that are not always smart enough to automatically import the required classes. Searching for Resize or Overlay, if taking into consideration the actual file path can be pretty challenging and not very intuitive. That's why we put all of the Actions under Cloudinary\Transformation namespace.

From the other side, if we flatten the transformations folder, it would be a disaster to maintain it.

composer-require-checker - to fix it, you'll probably need to add transformations package explicitely to your project.
I completely understand the goal of the tool.
From our side we have limited the major version dependency, so you won't have a surprise one day, when we have some breaking changes in the future.

Hope it answers your questions.

from cloudinary_php.