-
Notifications
You must be signed in to change notification settings - Fork 0
Should support ViewStore too. #1
Comments
I agree there may be some people who still prefer to use ReactiveSwift or RxSwift on SwiftUI, but that number would be so small compared to people who use Combine. I'm still open to the possibility of supporting SwiftUI in the future, but considering the time and energy I have, supporting UIKit is going to be my main focus for now. I'm going to keep this issue open for a while though, to see whether people are interested in the SwiftUI version. Good work on maintaining the ReactiveSwift version, I hope to be able to maintain this repo with the same quality 👍 . |
Thanks for your comments 🙏 Even if you don't support SwiftUI, the ViewStore is still a useful concept even for UIKit as shown in the doc comments for ViewStore. You can implement it without the |
FYI, there is another Rx port that you might be interested in, which does support ViewStore: https://github.com/dannyhertz/rx-swift-composable-architecture |
Oh nice, I can see the appeal in having the API to be as similar as possible compared to the original, keeping up is easy. In the meanwhile, I need to do extra work to keep up 😅. |
From the README:
The
ViewStore
is not just for SwiftUI. It's a very useful concept to use in UIKit too.One might assume that if the developer is targeting SwiftUI then Combine is obviously available, so there would be no need for this repo or the ReactiveSwift version. However, there are still good reasons to use ReactiveSwift or RxSwift even when Combine is available. Not least that both are OSS projects where bugs can be raised and fixed more quickly and transparently than in Combine.
The ReactiveSwift version of TCA does support ViewStore and SwiftUI btw.
The text was updated successfully, but these errors were encountered: