You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that unsafeCocoaAction was removed for the obvious reasons, but now it is unclear what to do with the programming of UI. Is there other sub-project with an extension of Action with unsafeCocoaAction that should be used for this purpose?
The text was updated successfully, but these errors were encountered:
Thanks, sounds reasonable. Do I understand it right that ReactiveCocoa will be only Cocoa-specific, while ReactveSwift will be its Swift based foundation? As a result, there will be no two Action classes in both ReactiveSwift and ReactiveCococa code-bases.
ReactiveCocoa is now built on top of ReactiveSwift. All the cross-platform bits are in ReactiveSwift; all the Cocoa-specific bits are in ReactiveCocoa. So Action is in ReactiveSwift, but CocoaAction is in ReactiveCocoa.
It seems that
unsafeCocoaAction
was removed for the obvious reasons, but now it is unclear what to do with the programming of UI. Is there other sub-project with an extension ofAction
withunsafeCocoaAction
that should be used for this purpose?The text was updated successfully, but these errors were encountered: