-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Gson 2.4, use newJsonWriter in GsonConverterFactory #1062
Comments
Gson was changed to expose this property (google/gson#700) so once it has its next release (this month or next, well before our v2.0) we can update to configuring a |
Waiting on 2.4 release which we're pushing for this coming week: google/gson#668. If it happens quick enough I can squeeze this into beta2! |
awesome, thanks!
|
Great, thank you! |
I can't speak English well, I have a question. How to solve |
Hello guys!
Recently I found out issue with null fields serialization during request call process. It is more looks like issue of Gson and there is pretty easy workaround of issue. So far issue lies within GsonConverterFactory which internally uses TypeAdapter instead of actual gson instance. I am not sure what was intent of using TypeAdapter, but such approach ignores extra configurations of Gson object such as
serializaeNulls: false
.Below is sample of code. Comment points out issue.
Suggested fix could be to use
gson instance
and not TypeAdapter.The text was updated successfully, but these errors were encountered: