Add more flexible target size options to ImageRequest.ThumbnailOptions #677
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the previous version, the only available option was
maxPixelSize
:The main issue with
maxPixelSize
is that it creates a thumbnail that fits the target size. For example, if you have a wide image with2000x400
pixel size and resize it tomaxPixelSize: 40
, the thumbnail will have the size40x8
pixels. There was no way to create a200x40
thumbnail, which is what you typically want to make sure the images have enough pixels to look good.In addition to
init(maxPixelSize:)
, there is now a new initializer with the parameters that directly matchImageProcessors.Resize
, so it's easy to switch between them.The default
contentMode
is.aspectFill
– the same as forImageProcessors.Resize
. And the default target size unit is.points
.