-
Notifications
You must be signed in to change notification settings - Fork 82
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
RxJava 3.1.x support #283
Comments
Can you pinpoint what is breaking exactly? IIRC the RxJava3 adapater doesn't use any of these classes explicitly. I'm also wondering about the need to support RxJava 3.0.x? |
The following classes are not available from RxJava 3.1.1
|
indeed, got it. so what's the play here? we have to break support for RxJava 3.0.x and 3.1.0 in a patch release :/ |
latest micronaut uses 3.1.5, I think it's better to upgrade. |
Do you have any update on supporting rxjava 3.1+? |
Hello ! |
This temporary downgrades rxJava from 3.1 to 3.0, due to reactor-addons incompatibility see reactor/reactor-addons#283
This temporary downgrades rxJava from 3.1 to 3.0, due to reactor-addons incompatibility see reactor/reactor-addons#283
@linux-china @marcambier and others, would you like to make a contribution? |
From RxJava 3.1.1 https://github.com/ReactiveX/RxJava/releases/tag/v3.1.1
The operator fusion-related interfaces and two atomic queue implementations have been promoted to standard, thus officially supported in the io.reactivex.rxjava3.operators package. ReactiveX/RxJava#7320
The package for following classes changed:
And RxJava3Adapter can not work with RxJava 3.1.x version.
The text was updated successfully, but these errors were encountered: