JSON All Or None Key Presence Check

Check all-or-none own member presence for an explicit key group; absent versus null is preserved.

Description

Check all-or-none own member presence for an explicit key group; absent versus null is preserved.

An all-or-none key group accepts either no members or the whole declared group. Partial presence fails.

When to use this tool

Check all-or-none own member presence for an explicit key group; absent versus null is preserved.

Prepare the supplied objectJson, groupKeys fields for this operation.
Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

Enter objectJson, groupKeys. Use the exact text syntax, units and index conventions explained below.
Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
Read result.presentKeys, result.allOrNone. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require a nonempty list of unique nonblank groupKeys, parse an object and return group keys found as own keys. allOrNone is true for zero present or the complete group.^[1]

Input field	Meaning and representation	Accepted input
objectJson	JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file.	Text
groupKeys	group keys.	At most 128 strings, each at most 128 UTF-16 code units

For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.

json

[
  {
    "field": "objectJson",
    "decoded": {
      "a": 1
    }
  }
]

Output field	Interpretation
result	Object containing the named outputs below.
result.presentKeys	The present keys list in the ordering and representation described above.
result.allOrNone	Flag for all or none under the exact condition described above.

json

{
  "input": {
    "objectJson": "{\"a\":1}",
    "groupKeys": [
      "a",
      "b"
    ]
  },
  "output": {
    "result": {
      "presentKeys": [
        "a"
      ],
      "allOrNone": false
    }
  }
}

Limitations and assumptions

Values are not checked and extra keys are allowed. The operation is not mutual exclusion or exactly-one validation.
Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Use a full schema validator when several shape, type and value constraints must work together. These tools apply the one declared presence, name, length or leaf policy and return explicit evidence of its scope.

References

Tool behavior and example: JSON All Or None Key Presence Check — tool.io

Similar or alternative tools

JSON Dependent Key Presence Check
Audit own-member dependencies when a trigger exists, including a null trigger value; do not infer semantic value requirements.
JSON One Of Key Presence Check
Check exactly-one own member presence across an explicit unique group; null values still count as present.