I’m also looking to add extra properties to transforms in my Cloudinary plugin that won't be removed during normalization. Ideally, I’d like to achieve this without using an extraOptions property to bundle non-native properties, by simply ensuring that these extra properties are not deleted from the transforms.

@thomasvantuycom I'm not sure it can be done without extraOptions with the current code. The way the transforms are cloned explicitly copies the properties across.

@brandonkelly Any thoughts on this?

@leevigraham to make sure we're on the same page, can you briefly describe your use-case and exactly what you're trying to do, outside of implementation?

Am I correct in saying that you're trying to have transforms that include non-native transform params when building the URL?

// renders something like: https://static-b.imgix.net/apples.jpg?blur=200&width=100
{{ asset.getUrl({ width: 100, blur: 200 }) }}

@timkelty basically yes that's the outcome.

The thing I'm trying to do at a more conceptual level is add extra properties to the transform so they can be picked up later in the before transform event. Currently they are lost in the Asset::getUrlsBySize() method because they are not known to Craft so Craft doesn't add them to the new transform.

The idea was that adding a single extraOptions property allows third parties to dump what ever they want in there and they will be passed along.

@leevigraham this is definitely something we want to refactor for Craft 6. Something like extraOptions can get the job done for now, but I'm not sure we want to go that route.

An alternative idea is to use create your own ImageTransform class, and use DI to swap it. I made some tweaks here to make that possible. Want to have a look and see if an approach like that might work for you instead?

The proposed solution works really well!

@timkelty I'll take a look at this today / tomorrow. I like the solution using a custom image transform class and getting the attributes.

@timkelty I'll take a look at this today / tomorrow. I like the solution using a custom image transform class and getting the attributes.

Sounds good! Its just a proof of concept as is, but probably pretty close to what you'd need. Let me know how it goes.

Additionally, if a refactor is planned for Craft 6, it might be worth considering a broader approach by generalizing the concept of image transforms to asset transforms. This would allow for more flexibility, as services like Cloudinary offer transformations for videos, PDFs, and various other file types.

Closed in favour of #15646