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
Upgrade to androidx #460
Comments
I was planning to update everything once 1.0 hits which should be any day now. We can bump the version to 3.0.0-SNAPSHOT and start the work |
Who's ready?!? |
How much would it offend people if this 3.0 was Kotlin-first as well? |
I am avoiding Kotlin, since I belive its going to be a waste of time converting all my code base to Kotlin and then converting it all over again to Flutter, a short while afterwards. I don't get offended if you go Kotlin first, I just don't get why to go to all the trouble if in a year or less people will be switching platforms anyways. Better focus the energy on making a Dart version and accelerate the future? |
You won't be converting your codebase to Flutter. |
Why not? I would love to hear your point of view about this, since you are so much more involved into Android than anyone I know. |
I don't want to have the discussion here. The easiest justification is that
it's a random third-party framework and not a first-party Android one.
…On Thu, Sep 27, 2018 at 1:12 PM feinstein ***@***.***> wrote:
Why not?
I would love to hear your point of view about this, since you are so much
more involved into Android than anyone I know.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#460 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEEEb2C_yT0SviFI74tuMkr5Cu_enINks5ufQb1gaJpZM4WWEND>
.
|
Yeah, this discussion will pollute this thread, my apologies, if you want to go to some reddit post or email exchange, please let me know. |
AndroiX is stable :) |
Any updates on a 3.0 snapshot? |
+1 for 3.0 version |
Is "android.enableJetifier=true" in gradle.properties sufficient for now to use RxBinding? |
This is done on |
The android x libraries are currently at release candidate versions so I figured it'd be a good time to discuss this. Hopefully migrating RxBinding will just involve a whole lot of renaming of imports, but what will this mean for the version number? This is technically a breaking change for some of the modules, so does this mean we change to 3.0?
Happy to some some legwork here, I just want to know how this should be approached. Are there any other considerations when migrating? Or is the plan to just let Jetifier handle things for now?
The text was updated successfully, but these errors were encountered: