ReactiveCocoa 2.0 #618
ReactiveCocoa 2.0 #618
Conversation
|
@ReactiveCocoa/reactivecocoa Do you guys think we should create some sort of migration guide for RAC 1.x -> 2.0? I personally think our deprecation messages and compiler errors will be good enough, but I'm receptive to the idea. |
|
I think a migration guide would be helpful. Even if it was just a list of deprecations, it's helpful to know what's changed if you're trying to decide when to upgrade. In my mind, it's the same material but it's presented at a different time for a different reason. |
|
@mdiep Well, this PR is meant to be the "what's changed" listing. A migration guide would be more about walking you through exactly how to update the code. |
|
I think the deprecation messages will be enough too, but I'm afraid we're biased because we've been exposed to the changes gradually. Users migrating from 1.x would have to deal with all the changes at the same time: it might be overwhelming and they might give up on upgrading and stick to 1.x, which would be really bad. |
|
Would the migration guide need to give coverage to each deprecation and each new method? Or just those we single out? Either way, I'd be happy to help write pieces. My hope is that there is a natural relationship between the amount of work needed to upgrade a codebase to RAC 2.0, and the comfort that the developer will have in making the changes. A developer who has only got their feet wet, will have fewer changes to make, whereas a developer that has used RAC more heavily will hopefully have a higher comfort level with handling the changes. Finally, either way, the various 2.0 announcements can include reminders to create Issues for any problems they run into. |
|
Discussion on the above moved to #679. |
…operties instead of the old initializer.
Re-enable RACBacktrace collection within RAC
|
👍 for me. |
…tion Fix RACCommand.enabled only completing after the input signal does
This means not using -autoconnect, and aligns more closely to the behavior of our other -replay… operators.
Reimplemented -switchToLatest redux
…nges -replayLazily behavior changes, -autoconnect refactoring
|
|
|
Really nice work guys! 🍷 |
|
+1 — congratulations to all of you on a great update! 🐶 |
|
Thanks again to everyone who helped! 🍻 |
|
🎊 |
|
✨ |
|
💥💥💥 |
|
📶 |
|
❤️ |
|
|
|
🎉 |
|
Congratulations!!! 🌟 |
|
I've tagged the official v2.0 release, since the RCs have seemed very good so far. Future improvements can come in minor or patch releases. |
|
🍻 |
|
🎆 |
|
🚀 |
|
🎉 🎊 |
|
@ashfurrow does that mean you're buying the first round? |
|
👏 👏 |
See the CHANGELOG for a list of all major and breaking changes, and information on how to update your project.
Performance improvements and critical fixes should continue to be applied to RAC 1.x until this branch is merged. After merging, 1.x versions will no longer be actively developed.
✨ Many thanks to everyone who's been helping! ✨