Skip to content
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

Moved to Kotlinx-serialization and updated Gradle and Kotlin #254

Closed

Conversation

BobbyESP
Copy link

@BobbyESP BobbyESP commented Nov 11, 2023

This PR initiates a significant upgrade by migrating our project to utilize Kotlinx-serialization instead of Jackson. This move brings enhanced data serialization capabilities and improving overall performance. Alongside this transition, the project's Gradle and Kotlin versions have been updated to higher stable releases, ensuring compatibility and leveraging the newest features available.

Changes Made:

  • Implemented Kotlinx-serialization for improved data serialization and deserialization.
  • Updated Gradle to version 7.4.2 (not the latest because it's needed to change something related to Maven and scaried of it in a big project XD so please, someone take a look).
  • Upgraded Kotlin to version 1.8.20 for language improvements and a little bit of modernization. Kotlin 1.7.22 its outdated.
  • Updated libraries versions

Why This PR?

Kotlinx-serialization Implementation: This change optimizes our data handling, enhancing efficiency and maintainability within the project.
Updated Gradle: The update ensures a more streamlined build process and better dependency management.
Latest Kotlin Version: Upgrading to the newest Kotlin version equips the project with the most recent language features and optimizations.

⚠️WARN!

I wasn't able to set up well the permissions request so that I added that permissions to the AndroidManifest.xml as well as in the DownloaderExampleActivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant