ivan.savytskyi
09/11/2020, 8:23 PMJsonLiteral has changed. It's now internal and body is no longer field on class. We have some business logic that was relying on getting access to raw value body to understand what type is that value. Now looks like there is no way to say what type was the value when JsonPrimitive was created. The only hint isString flag that doesn't really helps. What was the main rationale of hiding JsonLiteral and body? Is there any plans to introduce more subclasses of JsonPrimitive like JsonNumberPrimitive, JsonBooleanPrimitive to better represent the primitive value type?ivan.savytskyi
09/11/2020, 8:43 PMivan.savytskyi
09/11/2020, 8:45 PMVsevolod Tolstopyatov [JB]
09/16/2020, 6:33 PMWhat was the main rationale of hidingBecause it was here by mistake (actually, as workaround for compiler bug, but nevertheless). ExposingandJsonLiteral?body
Any type without clear restrictions and contracts it too permissive and potentially misleading.
Could you please elaborate on why isString + content is not enough for your usage?Vsevolod Tolstopyatov [JB]
09/16/2020, 6:40 PMivan.savytskyi
09/16/2020, 8:53 PMcontent: String doesn't provide info if original value was either boolean or long or doubleivan.savytskyi
09/16/2020, 8:58 PMivan.savytskyi
09/16/2020, 8:58 PM