This is the first alpha release of ReactiveCocoa 5.0. It targets Swift 3.0.
Introduction
Starting with 5.0, ReactiveCocoa primarily focuses on extending Cocoa and Cocoa Touch frameworks in Swift, on the ground laid by ReactiveSwift.
If you are looking for the Objective-C API, please visit ReactiveObjC.
Precautions
- Please be aware that more breaking changes are expected.
- Known issue: UIKit leaks.
About CocoaPods
The support is expected to land very very soon.
Hello Again!
Improved
- APIs have been updated for Swift 3
- No longer depends on ReactiveObjC.
- A parameterized
DynamicProperty, leveraging Objective-CidasAny. - A parameterized
CocoaActionwith its assumed sender type.
Added
- UIKit reactive extensions.
- Accessible via
.reactive. - Many UI components expose
BindingTargets for commonly written key paths. UIControlsubclasses expose signals of user initiated changes.UIControlexpose triggers for UI control events.- Convenient
UIControlbinding APIs withActions.
- Accessible via
- AppKit reactive extensions.
- Accessible via
.reactive. - Many UI components expose
BindingTargets for commonly written key paths. NSControlexpose signals of user initiated changes for all variants of values.NSControlsubclasses may expose specialised signals, e.g.NSTextField.reactive.continuousStringValues.
- Accessible via
- Foundation reactive extensions
- Accessible via
.reactive. - Intercepting selectors.
- Key path observations.
- Lifetime observations.
- Accessible via
Note
Many more changes since ReactiveCocoa 4! Future releases will aim to have more complete release notes.
Acknowledgement
Thank you for your support in ReactiveCocoa, and your patience in our Swift 3.0 release roadmap.
Thank you @dmcrodrigues, @ikesyo, @liscio, @mdiep, @NachoSoto, @RuiAAPeres, @sharplet and @andersio for the huge effort on the big bullet points of 5.0.
Thank you all contributors who helped maintain our documentations, and our nice community which helps the support effort.