JSON Array Homogeneity Audit
Audit immediate element-type homogeneity for every JSON array; an empty array is vacuously homogeneous, not evidence of a particular type.
Description
Audit immediate element-type homogeneity for every JSON array; an empty array is vacuously homogeneous, not evidence of a particular type.
An array may mix numbers, strings, objects and other JSON types even when its entries look similar. This audit inventories the immediate element types of every array in a document.
When to use this tool
Audit immediate element-type homogeneity for every JSON array; an empty array is vacuously homogeneous, not evidence of a particular type.
- Prepare the supplied documentJson 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 documentJson. 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.arrays. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Walk the parsed document and report each array's JSON Pointer, length, distinct immediate element types and homogeneous flag. Homogeneous is true when there are zero or one distinct types, including for an empty array.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| documentJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
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.
[
{
"field": "documentJson",
"decoded": [
1,
"x",
null
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.arrays | The arrays list in the ordering and representation described above. |
{
"input": {
"documentJson": "[1,\"x\",null]"
},
"output": {
"result": {
"arrays": [
{
"path": "",
"length": 3,
"types": [
"number",
"string",
"null"
],
"homogeneous": false
}
]
}
}
}Limitations and assumptions
- Arrays of objects can pass while their fields differ. The tool does not compare nested schemas or require any particular element type.
- Decoded JSON is bounded to 20,000 nodes and 32 nesting levels; record arrays have at most 128 records. Parsed number values use JavaScript floating point rather than arbitrary-precision decimal arithmetic.
- 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.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. 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
For document-wide requirements, combine these structural inventories with an explicit JSON Schema. Preserve the distinction between missing properties and null values, and between numbers and numeric-looking strings when building joins or indexes.
References
Similar or alternative tools
- json array length policy check
Audit all JSON array lengths against inclusive bounds; no inferred schema or scalar-array coercion.
- JSON Scalar Array Duplicate Spans
Report contiguous repeated typed-scalar array spans; do not conflate numeric/string values or nonadjacent duplicates.