MJPEG Streams and UIButton Image Filters
All issues associated with this milestone can be found using this filter.
Added
- New
.swift-version
file to repo and reactivated pod lib lint in Travis file.- Added by Christian Noon.
- The
OS_ACTIVITY_MODE
environment variable to disable excessive logging.- Added by Christian Noon.
- The new
CoreImageFilter
protocol and updatedBlurFilter
to conform to it.- Added by Florian Morello in Pull Request
#101.
- Added by Florian Morello in Pull Request
- The ability to the
AutoPurgingImageCache
to remove all images matching a URL request.- Added by Christian Noon in regards to Issue
#105.
- Added by Christian Noon in regards to Issue
ImageFilter
support to theUIButton
extension.- Added by gshahbazian in Pull Request
#129.
- Added by gshahbazian in Pull Request
- MJPEG support to
DataRequest
extension for streaming images.- Added by Robbie Trencheny in Pull Request
#185.
- Added by Robbie Trencheny in Pull Request
- Stream image test for
DataRequest
extension and updated docstrings.- Added by Christian Noon.
Updated
- The Alamofire submodule to the 4.0.1 release.
- Updated by Christian Noon.
- All cases of OSX to macOS throughout the project.
- Updated by Justin Jia in Pull Request
#181.
- Updated by Justin Jia in Pull Request
- Project settings by removing duplicate settings for individual targets.
- Updated by Christian Noon.
- Project and podspec so all files are compiled on all platforms.
- Updated by Christian Noon.
Fixed
- A typo in
placeholderImage
parameter in several UIButton APIs.- Fixed by Christian Noon in regard to Issue
#180.
- Fixed by Christian Noon in regard to Issue
- A
CIGuassianBlur
typo in one of the README code samples.- Fixed by Christian Noon in regard to Issue
#189.
- Fixed by Christian Noon in regard to Issue
Upgrade Notes
This release contains a non-backwards compatible change that fixes a typo in the UIButton
extension where placeholderImage
was misspelled in two APIs. Rather than push a MAJOR version release for a typo that people are generally getting incorrect, we decided to break semver here and fix the typo for everyone. Please note that we always try to follow semver as strictly as possible. However, this seemed like the best option given that users would continue to struggle with the typo throughout the lifespan of the 3.x releases.