We don't depend on ReactiveCocoa anymore (in Swift 3), just its new cousin: ReactiveSwift. It's a really cool project they're undertaking, separating ReactiveCocoa into two libraries.
Since we now have a different dependency, I think it's worth considering renaming the Moya/ReactiveCocoa subspec to Moya/ReactiveSwift. We'd also need to rename directories, Swift extension file names and extension names, and document it as well.
ashfurrow
All 11 comments
This is a major breaking change, will need docs in the changelog etc on how to migrate blah blah blah
orta
on 17 Sep 2016
Do we want to take this on for 8.0.0? This might be the best time to do so.
BasThomas
on 28 Nov 2016
Makes sense to me. I was thinking we could include it as two subspecs, and deprecate the old one in favour of the new. To avoid repeating ourselves in the podspec, we can have the old deprecated subspec simply have a dependency on the new one. Does that make sense?
ashfurrow
on 28 Nov 2016
That does make sense, but I am not sure how to do that myself. @Moya/contributors, anyone that wants to take a stab at this?
BasThomas
on 28 Nov 2016
8's going to be a big one 馃槷
AndrewSB
on 28 Nov 2016
Yup. I think we should be about good to go. Anything else we need for 8.0?
ashfurrow
on 29 Nov 2016
Waiting for an official release of ReactiveSwift is about it, I think.
BasThomas
on 29 Nov 2016
805 has been merged. 馃
BasThomas
on 29 Nov 2016
Cool cool. I don't see any more 1.0 issues on their repo, and they just had a new pre-release of 1.0 ship two days ago, so hopefully it won't be too long.
ashfurrow
on 29 Nov 2016
Let's hope so. 馃榾
BasThomas
on 29 Nov 2016
Seems like there's now one issue still open for 1.0 there, but I bet it won't take too long anymore.
BasThomas
on 29 Nov 2016
Related issues
sunshinejr
路
3Comments
gunterhager
路
3Comments
dimpiax
路
3Comments
JianweiWangs
路
3Comments
mwawrusch
路
3Comments
Most helpful comment
This is a major breaking change, will need docs in the changelog etc on how to migrate blah blah blah