(use na when API docs (Release notes, etc) do not need to be updated)
📝 Summary
Fix converter cannot take null value in request query and body
Before, if we send null value, the converter will take it out which I think it is not user's intention. If we add null to request body, it means we want to set it as null.
With above converter not taking null. it causes us
assume we have stream with latitude = 10, longitude = 100. and we update it with latitude = null. in the current API it will not update to null and also cause timezone and country code to be default
✅ DoD
(use na when API docs (Release notes, etc) do not need to be updated)
📝 Summary
null
value in request query and bodynull
to request body, it means we want to set it asnull
.null
. it causes uslatitude = 10
,longitude = 100
. and we update it withlatitude = null
. in the current API it will not update tonull
and also causetimezone
andcountry code
to be default