Detected unobvious plugin behavior:
For example (valid json)
[
{
"weight":{
"imperial":"9 - 14",
"metric":"4 - 6"
},
"image":{
}
},
{
"weight":{
"imperial":"12 - 18",
"metric":"5 - 8"
},
"image":{
"id":"0SxW2SQ_S",
"width":800,
"height":1203,
"url":"https://smth.jpg"
}
}
]
Plugin will generate 4 classes and this one will brake everything:
data class listItem(
val image: Image,
val weight: Weight
)
because Image must be nullable in this case.
Retrofit can handle this item without any error, but when I will try to [ map {} ] list of this items, map function will throw unchecked error or Unit idk(there are no any errors tho) just nothing on result if one of the items during mapping throws an error.
If this type were nullable I could immediately see where the error might occur with this particular json, the analysis of which I delegated to the plugin.
Detected unobvious plugin behavior:
For example (valid json)
Plugin will generate 4 classes and this one will brake everything:
because Image must be nullable in this case.
Retrofit can handle this item without any error, but when I will try to [ map {} ] list of this items, map function will throw unchecked error or Unit idk(there are no any errors tho) just nothing on result if one of the items during mapping throws an error.
If this type were nullable I could immediately see where the error might occur with this particular json, the analysis of which I delegated to the plugin.