Are proguard rules really needed if you use `Type....

# serialization

[ansman]

Are proguard rules really needed if you use Type.serializer() on Jvm/Android? In what cases would a reflective serializer be used then?

[jw]

Here's mine for Retrofit which uses that API: https://github.com/JakeWharton/SdkSearch/blob/master/frontend/android/src/main/shrinker-rules.pro#L25-L37

[ansman]

What’s the last one for?

[jw]

the last one is a two-parter because it's an if

[jw]

if a companion has a serializer function, keep the static companion field on the original type

[jw]

the reflection inside kotlinx.serialization will basically do KClass.getClass().getField("Companion").getMethod("serializer")

[jw]

Which makes me wonder if it works with named companions... And I should probably change the rule to not match on the field name explicitly. Will need to test both.

[ansman]

So it uses reflection even when doing Type.serializer()?

[ansman]

Sorry, I realize I used a horrible name. Should’ve used MyClass.serializer()

[jw]

oh, no that doesn't use reflection

[ansman]

Cool, my serializers are only for internal consumption so I should be good