Description
Require every segmentKinds entry to be object or array and count the array entries as arrayDepth.
JSON Pointer separates path tokens with slashes and escapes literal slash and tilde inside member names. The empty pointer denotes the document root; an empty token can name an actual empty-string member.
Require every segmentKinds entry to be object or array and count the array entries as arrayDepth.
When to use this tool
Use JSON Path Array Depth when you need a pointer token, depth, or representation check.
How to use the tool and how it works
- Enter segmentKinds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read arrayDepth. Use the output convention below.
Require every segmentKinds entry to be object or array and count the array entries as arrayDepth.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| segmentKinds | Segment Kinds | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| arrayDepth | Array Depth | Required. Safe integer. |
{
"input": {
"segmentKinds": [
"object",
"array",
"array"
]
},
"output": {
"arrayDepth": 2
}
}Limitations and assumptions
- Container kinds are caller supplied; the tool does not parse a path or inspect a JSON document.
- 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 pointer parser and resolve against the actual document when existence or array access matters.
References
Similar or alternative tools
- JSON Pointer Root Distance
Count zero segments for root or the slash-separated token count otherwise.
- JSON Pointer Relative Up Count Field
Parse a canonical nonnegative up count of at most nine digits followed by hash, a slash path, or nothing.