JSON Container Width Profile
Profile immediate child counts of all JSON containers, retaining empty arrays and objects.
Description
Profile immediate child counts of all JSON containers, retaining empty arrays and objects.
Container width counts immediate children, while depth counts nested levels. A width profile helps identify unusually broad objects or arrays inside a JSON payload.
When to use this tool
Profile immediate child counts of all JSON containers, retaining empty arrays and objects.
- 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.containers. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Walk every parsed JSON node. For each object or array, emit its JSON Pointer, container type and width: own enumerable key count for objects, element count for arrays. Include the root when it is a container.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": {
"a": []
}
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.containers | The containers list in the ordering and representation described above. |
{
"input": {
"documentJson": "{\"a\":[]}"
},
"output": {
"result": {
"containers": [
{
"path": "",
"type": "object",
"width": 1
},
{
"path": "/a",
"type": "array",
"width": 0
}
]
}
}
}Limitations and assumptions
- Scalar leaves have no width row. Object key order follows the parser's JavaScript enumeration rules; the profile does not measure encoded byte size.
- 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 Depth Profile
Profile JSON node depths with root depth zero, counting containers and scalar leaves explicitly.
- json all or none key presence
Check all-or-none own member presence for an explicit key group; absent versus null is preserved.