Encountered a practical issue in converting JsonNode to msgpack Value, which was mentioned in #12.
In Json, special reasons to once convert into String and then parse that. Not to directly convert JsonNode to msgpack Value?
If the JsonNode value is empty in JacksonServiceValue#jsonValue, value.asText() goes an empty String, and an empty String cannot be parsed by the JSON Parser. :(
If we use toString instead of asText, it goes "{}". It might be the reason why toString was used originally?
We have two choices:
Get this simply back to toString.
Convert JsonNode directly to msgpack Value.
2 may be finally better, but 1 can be a short-term solution.
Encountered a practical issue in converting
JsonNode
to msgpackValue
, which was mentioned in #12.If the
JsonNode value
is empty inJacksonServiceValue#jsonValue
,value.asText()
goes an emptyString
, and an emptyString
cannot be parsed by the JSON Parser. :(If we use
toString
instead ofasText
, it goes"{}"
. It might be the reason whytoString
was used originally?We have two choices:
toString
.JsonNode
directly to msgpackValue
.2 may be finally better, but 1 can be a short-term solution.
Can I have your thoughts? @muga