JSON / presence / handoff
Separate “missing” from empty JSON values
Review missing fields, null, empty strings, arrays and objects as different presence states. Use synthetic cases only; no user JSON is accepted.
Presence is not one empty state
Whether a field is absent, explicitly null, or a typed empty value changes defaults, updates and required checks.
missing ≠ null ≠ "" ≠ [] ≠ {}| case | What to review |
|---|---|
missing-field | The field does not exist; a default may apply. |
null-value | The field exists and explicitly carries null. |
empty-string | A string exists and has zero length. |
empty-array | An array exists with zero elements. |
empty-object | An object exists with zero keys. |
explicit-value | A value exists and is part of the handoff. |
Review order
- Check whether the field exists.
- If it exists, distinguish null from a typed empty value.
- Record the receiver’s default and required rules separately.
- Do not guess about an ambiguous input; hand it back for review.
This page uses synthetic fixtures only. There is no upload, external request, storage, or user JSON parsing.