Replies: 2 comments 1 reply
|
You should definitely avoid using Gson in a Kotlin project. I believe adding an implementation based on a discouraged API is not a good idea. In the case of Gson, its usage may lead to unexpected behavior and runtime errors. |
1 reply
|
I understand the concerns about Gson, but not everyone is working with a shiny new codebase that can fully leverage kotlinx.serialization. 😄 Even Ktor supports Gson serialization for similar reason, legacy compatibility and flexibility. I think keeping this example in the discussion could help folks with older projects who need a quick solution. 🙏 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi 👋
I was exploring the supabase-kt library and noticed that there isn’t a built-in serializer using Gson. It would be useful to have an implementation like the following:
Is there a reason Gson isn’t included as an option in supabase-kt?
Thanks for your work on this library.
All reactions