Optimize condition order to avoid unnecessary method calls in AutoMapper

[tpatartmajeur]

This PR reorders the generated condition checks in the generate() method to prioritize the customCondition() check before other standard conditions.

In the generated mapper code, this change allows custom condition to occur earlier. As a result, potentially heavy methods, such as those that may trigger database queries are not executed if the custom condition fails.

Before:

if (isAllowedAttribute(...) && groupsCheck(...) && customCondition(...)) { // DB hit
   $result->someProperty = $value->someMethod(); // DB hit
}

After:

if (customCondition(...) && isAllowedAttribute(...) && groupsCheck(...)) {
    $result->someProperty = $value->someMethod(); // DB hit only if needed
}

[Korbeil]

Seems good to me.

Could you update the CHANGELOG to add a quick line about your change please ? 🙏

[tpatartmajeur]

@Korbeil Done

[Korbeil]

Thanks for your contribution @tpatartmajeur ! 🙏

[tpatartmajeur]

Hi @Korbeil! Do you know when the next release is planned? We’re scheduling a production deployment soon, and having the changes from this MR included would be a great plus.