So I used Gson and got this - `java.lang.IllegalAr...

# android

[adams2]

So I used Gson and got this - java.lang.IllegalArgumentException: Parameter specified as non-null is null: method kotlin.jvm.internal.Intrinsics.checkParameterIsNotNull, parameter $receiver

[adams2]

does this mean I shouldn't use gson if it swaps stuff out to null behind my back?

[adams2]

hmm maybe I need to make some example code to understand that error better

[reline]

yeah, I would say that when fields are nullable in json making your fields nullable is the best idea when mapping to a json response

[adams2]

the field should not be null though, the field should always be present. But json doesn't have a way to specify nullable or not, so it being null is possible.

[adams2]

What I'd like to do is handle this possibility in only one place, instead of having to deal with the property being nullable everywhere

[adams2]

might end up doing this https://stackoverflow.com/questions/21626690/gson-optional-and-required-fields

[adams2]

hmm how do I check kotlin nullability using reflection... 🤔

[adams2]

ooo found this https://github.com/sargunv/gson-kotlin

[adams2]

huh kotlin-reflect is big

[adams2]

guess I'll make a new annotation

[adams2]

oh https://github.com/Kotlin/kotlinx.reflect.lite

[gildor]

Java json mapping libraries work not so good with nullability.
And there is no good solution, as I know, that doesn’t use Kotlin Reflections
We use AutoValue + auto-value-gson plugin to achieve nullability validation

[gildor]

Also, respect of nullability from you API could help a lot

[adams2]

maybe I should just make a DTO layer