Details
-
Story
-
Resolution: Fixed
-
High
-
5.1
-
None
-
Aconcagua Sprint 1
Description
Image variants need to be exposed via REST. However, for multiple reasons, they can't be exposed directly from a vnd.ez.api.Content response.
The main problem is that doing so would imply iterating over every alias for every image in the content, and generate the alias before outputing its URI. In terms of performances, this just won't work.
The first step is to provide specifications towards a solution.
Attachments
Issue Links
- discovered while testing
-
EZP-20769 REST v2: Reading object containing ezimage datatype returns hardcoded ( and wrong ) results
- Closed
- relates to
-
EZP-23719 Missing contentType, width, height and fileSize properties in to the output of the load image variation REST response
- Closed
-
EZP-22017 Missing API to load an image variation
- Closed
- links to
- mentioned in
-
Wiki Page Loading...