All Versions
144
Latest Version
Avg Release Cycle
19 days
Latest Release
101 days ago

Changelog History
Page 10

  • v3.2.0

    November 07, 2016

    ➕ Add

    • A new option to ignore placeholder and keep current image while loading/downloading a new one. This would be useful when you want to display the earlier image while loading a new one. 494
    • A disk cache path closure to let you fully customize the disk cache path. #499

    🛠 Fix

    • 🚚 Move methods which were marked as open to their class defination scope, to avoid the compiler restriction when overridden. #500

  • v3.1.4

    October 19, 2016

    🛠 Fix

    • 🛠 Fix a problem that CIImageProcessor not get called when feeding data to the processor. #485

  • v3.1.3

    October 06, 2016

    🛠 Fix

    • A compiling time issue. Now the compile time of Kingfisher should drop dramatically. #467
    • kf wrapper of all Kingfisher compatible types now a class instead of struct, to make mutating opearation on it possible. #469

    ✂ Remove

    • 🚚 requestModifier of ImageDownloader is removed to prevent leading to misunderstanding.

  • v3.1.1

    September 28, 2016

    🛠 Fix

    • 🐎 An issue which prevents using multiple image processors at the same time. Now you can use different ImageProcessor at the same time for an image, while keeping high performance since only one downloading process would be fired. #460
    • A crash when processing some images with built-in ResizingImageProcessor and OverlayImageProcessor while the input images not having a standard format. #440, #461
    • ImageCache could accept a path extension as key now. #456

  • v3.1.0

    September 21, 2016

    ➕ Add

    • ➕ Add kf namespace for all extension APIs in Kingfisher. Now no need to worry about name conflicting any more. #435

    🛠 Fix

    • Mark AnimateImageView to open so you can extend this class again. #442
    • ⚡️ Update demo code to adopt iOS 10 prefetching cell feature and new cell life cycle. #447

    ✂ Remove

    • 🗄 Since kf namespace is added, all original kf_ prefix methods are marked as deprecated.

  • v3.0.1

    September 14, 2016

    ➕ Add

    • 👀 Swift 3 compatibility. This version follows Swift 3 API design guideline as well as contains a lot of breaking changes from version 2.x. See Kingfisher 3.0 Migration Guide for more about how to migrate your project to 3.0. Kingfisher 2.6.x is still supporting both Swift 2.2 and 2.3.
    • 👀 Image Processor. Now you can specify an image processor and it will be used to process images after downloaded. It is useful when you need to apply some transforming or filter to the image. You can also use the processor to support any other image format, like WebP. See Processor section in the wiki for more. The default processor should behave the same as before. #420
    • Built-in processors from simple round corner and resizing to filters like tint and blur. Check Built-in processors of Kingfisher for more.
    • Cache Serializer. CacheSerializer will be used to convert some data to an image object for retrieving from disk cache and vice versa for storing to disk cache.
    • 🆕 New indicator type. Now you should be able to use your own indicators. #430
    • ImageDownloadRequestModifier. Use this protocol to modify requests being sent to your server.

    🛠 Fix

    • Resource is now a protocol instead of a struct. Use ImageResource for your original Resource type. And now URL conforms Resource so the APIs could be clearer.
    • 0️⃣ Now Kingfisher cache will store re-encoded image data instead of the original data by default. This is needed due to we want to store the processed data from ImageProcessor. If this is not what you want, you should supply your customized instanse of CacheSerializer.

    ✂ Remove

    • 🚚 KingfisherManager.init is removed since you should never create your own manager.
    • 🚚 cachedImageExistsforURL in ImageCache is removed since it introduced unnecessary coupling. Use isImageCached instead.
    • 🚚 requestModifieris removed. Use.requestModifierand pass aImageDownloadRequestModifier`.
    • 🚚 kf_showIndicatorWhenLoading is removed since we have a better and flexible way to use indicator by kf_indicatorType.

  • v3.0.0

    September 14, 2016

    ➕ Add

    • 👀 Swift 3 compatibility. This version follows Swift 3 API design guideline as well as contains a lot of breaking changes from version 2.x. See Kingfisher 3.0 Migration Guide for more about how to migrate your project to 3.0. Kingfisher 2.6.x is still supporting both Swift 2.2 and 2.3.
    • 👀 Image Processor. Now you can specify an image processor and it will be used to process images after downloaded. It is useful when you need to apply some transforming or filter to the image. You can also use the processor to support any other image format, like WebP. See Processor section in the wiki for more. The default processor should behave the same as before. #420
    • Built-in processors from simple round corner and resizing to filters like tint and blur. Check Built-in processors of Kingfisher for more.
    • Cache Serializer. CacheSerializer will be used to convert some data to an image object for retrieving from disk cache and vice versa for storing to disk cache.
    • 🆕 New indicator type. Now you should be able to use your own indicators. #430
    • ImageDownloadRequestModifier. Use this protocol to modify requests being sent to your server.

    🛠 Fix

    • Resource is now a protocol instead of a struct. Use ImageResource for your original Resource type. And now URL conforms Resource so the APIs could be clearer.
    • 0️⃣ Now Kingfisher cache will store re-encoded image data instead of the original data by default. This is needed due to we want to store the processed data from ImageProcessor. If this is not what you want, you should supply your customized instanse of CacheSerializer.

  • v2.6.0

    September 12, 2016

    ➕ Add

    • 👌 Support for different types of indicators, including gif images. #425

  • v2.5.1

    September 06, 2016

    🛠 Fix

    • 🛠 Fix a possible trap of range making in prefetcher. #422

  • v2.5.0

    August 29, 2016

    ➕ Add

    • 👌 Support for Swift 2.3