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
Remove no longer needed compat methods #5581
Conversation
Do you have an official source for that? The function does not look like we are supposed to use it directly and this SO post says it's not part of the public API. |
The post is saying that Anyway, Furthermore, |
7a892ca
to
bad7d92
Compare
Yeah, I think that would be good. The behavior should not be changed. The change currently breaks the statistics screens.
Oh, right. Sorry. I somehow mixed up the additions vs deletions and thought you are doing the exact opposite. Your change is obviously what we want/should do 👍 |
No worries lol. I'll get to flipping the compares when I can :) |
bad7d92
to
ca7f2d2
Compare
@ByteHamster Done 👍 |
Thanks! |
This pull request has been mentioned on AntennaPod Forum. There might be relevant details there: https://forum.antennapod.org/t/antennapod-2-5-release-notes/1636/1 |
With the recent bump of the minimum supported OS version from 16 to 19 (which makes me pretty happy), there are quite a few compat methods we no longer need to use, as the internal checks they do are for versions below 19.
Some side notes:
AppCompatResources.getDrawable
callsAppCompatDrawableManager.get().getDrawable
internally, and is what's supposed to be used anyway.CompareCompat.compareLong
's code was (or the comments were) incorrect for some reason. Thegreater than
andless than
symbols were flipped and didn't match up with the method's comments, causing the actual behavior to be equal toLong.compare(long2, long1)
instead ofLong.compare(long1, long2)
like the comments say. I can only assume that was a mistake by the original contributor. Should I also flip these, then, since that was the behavior of the removed method?