You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BitmapUtils is responsible for decoding bitmaps, but currently contains deprecated API usages. To ensure the code is up-to-date and maintainable, we should update the API usage and consider converting the code to Kotlin.
Additionally, performance improvements can be made by utilizing newer APIs and optimizing the existing logic to handle bitmaps more efficiently.
The text was updated successfully, but these errors were encountered:
I'd love to work on this issue. I plan to update the deprecated API usages and optimize the bitmap handling logic using newer APIs. I’ll also explore converting the code to Kotlin for better maintainability.
@Onkar755 Hey, thank you so much for your message and support! 💯
When working on the BitmapUtils class, please focus only on making improvements to BitmapUtils. It would be great if you could keep the changes minimal to ensure the PR stays small and helps prevent any regressions.
Thanks for the clarification. Just to confirm, would you prefer keeping the code in Java for now with the API updates and optimisations, or should I also proceed with converting the BitmapUtils class to Kotlin in a separate PR?
Thanks for the clarification. Just to confirm, would you prefer keeping the code in Java for now with the API updates and optimisations, or should I also proceed with converting the BitmapUtils class to Kotlin in a separate PR?
Hey. You can convert to the Kotlin. Thank you so much for your support 💯
BitmapUtils is responsible for decoding bitmaps, but currently contains deprecated API usages. To ensure the code is up-to-date and maintainable, we should update the API usage and consider converting the code to Kotlin.
Additionally, performance improvements can be made by utilizing newer APIs and optimizing the existing logic to handle bitmaps more efficiently.
The text was updated successfully, but these errors were encountered: