Accept "null" as valid value
Opened this issue · 4 comments
I think the package needs to accept null as a valid value and have its own style.
Actually, I don't suggest setting a value as null. I was really tired of Null Exception T T. Which a value is 'null' means the Object didn't include the value.
But it could be some Jason that has null as a value. I mean when we copy some Json (especially the large one) from everywhere it's needed to not show error, right.
Imagine a situation where we want to submit null as an already not null saved value. what should we do? (It only saves keys that exist in JSON).
The first point I understand. Yeah, you're right that the editor needs to support the null type and will be UI-friendly. But the output Object couldn't have the null value. Then we can use Object.containsKey(key) to adjust if the key existed or if the key-value was null. It will be safe.
+1
some JSON has null as a value. Currently, the package doesn't accept that, which causes bugs. We cannot use this package without having the full JSON valid value range.