Support generation without @SerializedName
Closed this issue · 2 comments
SpicyCactuar commented
It's particularly useful, for example, when combining Retrofit
with GSON
and using snake case policy for serialization/deserialization.
I know it couples the names of the fields with API JSON names, but as long as it keeps being a conscious decision, it can live with it in order to not pollute the POJO class.
nvinayshetty commented
This is already supported. Please select type as Pojo from right panel instead of the default Gson which is checked by default.
SpicyCactuar commented
Lovely, Thanks!