Return resized image paths

[paliarush]

As a Magento developer, I need GraphQL API to return resized image paths so that I can render storefront experiences with correctly sized images.

Acceptance criteria:

1. GraphQL returns original image paths
2. GraphQL returns resized image paths if the images have been resized
3. Changes are covered with web API functional tests. See \Magento\GraphQl\Catalog\ProductViewTest::testQueryAllFieldsSimpleProduct as an example.

[paales]

Although I agree that this would be a nice feature, this feature is not exclusive to GraphQL and might be more interesting as a general API. I had created the feature request earlier here: magento/community-features#44

We have recently implemented https://github.com/h2non/imaginary as an api for one of our customers, but it would be nice if such a thing could be directly in Magento. The most imporant part is that a serious frontend requires modern image formats for a fast website. Spending 50% extra on images because you have to use .jpg isn't a good idea.

For any serious client we revamp the functionality to:

• Use render-dependent images (rendered large, downloads a large image, rendered small, download a small image).
• Use connection-dependent images (slow connection, low quality image, fast connection, high quality image)
• Serve jpg/png/webp based on it's context
• Make sure all images are als optimized as possible.

To achieve this we use a client side webcomponent that requests the right image. It adds additional query parameters to the URL to download the correct one.

The advantage of using a query parameter is that you don't need to do a query to fetch the URL of a certain size of image (the size it is rendered).

[id-mitchell]

I would find this functionality very useful to have as an option. I'm not sure requesting image sizes through GraphQL like this would be the best solution for a larger project, but again I think it would be very useful regardless. Based on the fact that this is still open and marked "for-grooming" I'm assuming this hasn't made it's way into any sort of development process yet? I didn't see anything in the docs or in the 2.3.0 codebase at least.

[paliarush]

@id-mitchell we will probably focus on this after checkout coverage is done.

[naydav]

• @nrkapoor