-
Couldn't load subscription status.
- Fork 17
IBX-9727: Fixed strict types of Core Imagine integration layer #619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weâll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
203acad to
193bee5
Compare
7aa5041 to
dd6f888
Compare
193bee5 to
72a596b
Compare
72a596b to
c824970
Compare
âŠimplementations
dd6f888 to
5a1342f
Compare
|
| 'value' => new ImageValue([ | ||
| 'id' => 'images/6/8/4/0/486-10-eng-GB/photo.jpg', | ||
| ]), | ||
| ]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something is wrong with indentation here
Caution
Related PRs:
Description:
Follow up to #613. IO layer touches
\Ibexa\Bundle\Core\Imaginenamespace which contains Imagick/Gmagick image manipulation integration.Contracts fixed:
\Ibexa\Contracts\Core\Variation\VariationHandler\Ibexa\Core\FieldType\Image\AliasCleanerInterface(internal)Outside of the namespace, fixed:
\Ibexa\Core\FieldType\Image\NullAliasCleaner\Ibexa\Core\MVC\Symfony\Templating\Twig\Extension\ImageExtensionBC breaks:
\Ibexa\Contracts\Core\Variation\VariationHandler::getVariationnow throws uniformly\Ibexa\Contracts\Core\Repository\Exceptions\InvalidArgumentExceptioninstead of PHP's nativeInvalidArgumentException. Some implementations already threw the Repository one, but the main implementation threw the PHP's native one. It makes more sense for it to be the Repository exception. However, as can be inferred from the diff, Twig functions:ibexa_image_aliasandibexa_content_field_identifier_image_assetwere affected.For QA:
Scope: image variation generation.
Regression tests:
Documentation:
Probably a note about the breaking change.