Combine Support

We've received many questions regarding Combine (https://github.com/uber/RIBs-iOS/issues/20#issuecomment-3177327815, https://github.com/uber/RIBs-iOS/issues/20#issuecomment-3197210637, https://github.com/uber/RIBs/issues/346, ), either about making an integration with it or about rewriting the whole framework with Combine instead of RxSwift.

As @rudro mentioned here: https://github.com/uber/RIBs/issues/346#issuecomment-1230952099, in hindsight, it was a good call not to go with Combine.

We had a conversation about it recently and reaffirmed that there is no need or plans to move RIBs framework to Combine. For backward compatibility reasons and because there is no inherent advantage in doing so, as RIB's usage of Rx is very light.

If you're seeking Combine support with RIBs you can check out https://github.com/DevYeom/ModernRIBs.

Potentially, we will attempt to implement some form of Combine compatibility in the form of convenience methods and mappers/wrapper, akin to https://github.com/CombineCommunity/RxCombine (perhaps by using RxCombine) but this is the last on the list of priorities after SwiftUI and Swift Concurrency (async/await) support and other features.

The issue describes possible Combine compatibility but states there are no current plans to rewrite RIBs and that this is a low priority. Start by reading the linked discussions and the references to SwiftUI, Swift Concurrency, RxSwift, and RxCombine. There are no files or tests named; completion is not defined beyond a future project decision.