This is a maintenance release of ReactiveCocoa 5.0. Compatible with Swift 3.0 and 3.1.
Users who use KVO on computed dependent keys are recommended to update to 5.0.3 as soon as possible due to the potential impact of the bug.
Addition
-
New KVO API:
NSObject.reactive(self:).signal(forKeyPath:)
. (#3413, kudos to @Burgestrand) -
New binding targets for
UINavigationItem
andUITabBarItem
. (#3444, kudos to @Marcocanc) -
New binding targets for
UIFeedbackGenerator
and its subclasses. (#3447, kudos to @Marcocanc)
Changes
-
NSObject.reactive(self:).values(forKeyPath:)
is deprecated and replaced byNSObject.reactive(self:).producer(forKeyPath:)
. (#3413) -
The KVO API now supports object values that are of native Swift classes properly. (#3439, kudos to @andersio)
-
A bug that could lead to deadlocks and unexpected
nil
in the KVO API on any arbitrary key path was fixed. (#3439) -
Continuous text signals of
UITextField
now emits the latest value for all editing events emitted. In other words, replacements due to autocompletions are now covered by the signals. (#3442 , kudos to @andersio) -
Fixed a ObjC swizzling bug that caused
ActionProxy
not working well with KVO and RAC method interception. (#3435, kudos to @andersio)
Note
The binary was built with Swift 3.1 and ReactiveSwift 1.1.1.
Acknowledgements
Kudos to @mdiep, @NachoSoto, @eimantas, @sharplet, @ikesyo and @andersio who helped review the pull requests and contribute to the documentations.