You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since there are two possible ways to expose XML empty element (like "" -- but not ""), it seems reasonable to allow configuration of how this is to be exposed.
Due to backwards compatibility reasons, setting should default to true, so that by default empty element would be exposed as equivalent of JSON null token (JsonToken.VALUE_NULL).
But disabling of this feature would instead expose it as JsonToken.VALUE_STRING with text value of "" (empty String).
The text was updated successfully, but these errors were encountered:
I have been hoping to finalize 2.9.0 for a while now; 2.9.0.pr4 is meant as the last pre-release version.
I am now hoping to get 2.9.0 out by end of July 2017.
Since there are two possible ways to expose XML empty element (like "" -- but not ""), it seems reasonable to allow configuration of how this is to be exposed.
Due to backwards compatibility reasons, setting should default to
true
, so that by default empty element would be exposed as equivalent of JSONnull
token (JsonToken.VALUE_NULL
).But disabling of this feature would instead expose it as
JsonToken.VALUE_STRING
with text value of "" (empty String).The text was updated successfully, but these errors were encountered: