-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/migrate to rxjva 3 #317
Feature/migrate to rxjva 3 #317
Conversation
@dlew alternatively we can just remove rxlifecycle-navi module and drop navi support. EDIT: Found this: 69b8a11#diff-04c6e90faac2675aa89e2176d2eec7d8R141 It's time to remove navi ;) |
Thanks for the PR - just a warning that I'm very busy right now and probably won't be able to review it for a bit. I'll put it on my queue, just know I'm not ignoring this. |
Thank you for your contribution @klamborowski. Before merging this to master, should we create a separate branch for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's nice that all this really required were some class import changes.
gradle.properties
Outdated
POM_DEVELOPER_NAME=Dan Lew | ||
|
||
android.enableJetifier=true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's causing us to need the Jetifier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not required, I will remove it in next push.
gradle.properties
Outdated
@@ -1,5 +1,5 @@ | |||
GROUP=com.trello.rxlifecycle3 | |||
VERSION_NAME=3.1.0-SNAPSHOT | |||
VERSION_NAME=3.3.0-SNAPSHOT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should bump to 4.0.0 (since this is a major change).
(Yeah, it's disappointing that it'll be out-of-sync with RxJava3 but... it already was, since RxLifecycle 3.x was compatible with RxJava 2.x!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
@@ -42,7 +42,6 @@ public void noEvents() { | |||
stream.onNext("1"); | |||
stream.onNext("2"); | |||
testSubscriber.assertValues("1", "2"); | |||
testSubscriber.assertNotTerminated(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
assertNotTerminated()
was removed, but assertNotComplete()
remains. As far as I can tell, that would be the best replacement, since other tests in the same class call assertComplete()
- the complete/not complete dichotomy is one worth testing as a result.
(Making this comment here, but assertNotTerminated()
has been removed from a bunch of tests.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
14312a8
to
c183d22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, thanks for the work!
I'll work on getting a release out soon.
Working on migration to rxjva3. Currently WIP and waiting for navi migration: trello-archive/navi#106
Issue #315