Skip to content

Conversation

David-Development
Copy link
Member

Follow up from: #1435 - sounds like we don't need the GSON rules anymore. I've removed them and tested the debug build without the GSON rules and it seemed to work just fine (we don't use @SerializedName because we do the deserialization mostly manually)

Added default ProGuard / R8 rules (@​Marcono1234, #2397, #2420; @​sgjesse, #2448; @​sfreilich)
If you are using ProGuard or R8 (for example for Android projects) you might not need any special Gson configuration anymore if your classes have a no-args constructor and use @SerializedName for their fields.

Signed-off-by: David Luhmer <david-dev@live.de>
Signed-off-by: David Luhmer <david-dev@live.de>
@David-Development David-Development merged commit 0291b77 into master Jun 12, 2024
@Unpublished Unpublished deleted the cleanup-proguard-gson branch June 23, 2024 09:13
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.

2 participants