Description
Parse objectJson as an object and classify the literal key as missing, empty-string, null, or other using own-property presence before value checks.
A JSON member can be absent, present with null, or present with an empty string. Testing own-property presence preserves those distinctions instead of relying on truthiness.
Parse objectJson as an object and classify the literal key as missing, empty-string, null, or other using own-property presence before value checks.
When to use this tool
Use JSON: JSON Empty String Versus Missing Tag when you need an explicit object-member presence or key comparison.
How to use the tool and how it works
- Enter objectJson, key. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Parse objectJson as an object and classify the literal key as missing, empty-string, null, or other using own-property presence before value checks.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| objectJson | Object Json | Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| key | JSON-array serialization of the stated identifying fields, preserving exact strings. | Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
| result.state | State | Calculated result member: string. |
{
"input": {
"objectJson": "{\"a\":\"\"}",
"key": "a"
},
"output": {
"result": {
"state": "empty-string"
}
}
}Limitations and assumptions
- These states are distinct; this does not normalize keys or interpret other falsy values as missing.
- Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use a complete schema and document comparison when conditional requirements or nested structures matter.
References
Similar or alternative tools
- JSON Schema Required Single Key Check
Parse objectJson as a plain JSON object and test Object.hasOwn for the literal key.
- List Group Key Literal Null Flag
Parse keyJson and compare its value separately with literal null and the string null.