Description
Decode the bounded typed tuple key dialect, rejecting incomplete/trailing fields and preserving scalar types; no arbitrary JSON object keys.
An opaque key’s representation can affect equality and ordering even when its underlying value is unchanged. Delimiter joining can be ambiguous, fixed-width padding can preserve numeric order within agreed bounds, and typed length-prefix framing keeps scalar types distinct. Lengths in this family count UTF-16 code units unless a different unit is stated.
Decode the bounded typed tuple key dialect, rejecting incomplete/trailing fields and preserving scalar types; no arbitrary JSON object keys.
When to use this tool
Use this tool to decode the bounded typed tuple key dialect, rejecting incomplete/trailing fields and preserving scalar types; no arbitrary JSON object keys.
How to use the tool and how it works
- Enter key using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.values. Use the ordering, boundary rules and absence conditions described below.
Parse the canonical tuple count and each member’s length prefix, decode its typed scalar, and require the entire key to be consumed.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| key | One encoded or opaque key, interpreted under the operation’s exact convention. | Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.values | Decoded JSON scalar tuple values in original order. |
{
"input": {
"key": "t:3:3:n:15:s:1:12:z:"
},
"output": {
"result": {
"values": [
1,
"1",
null
]
}
}
}Limitations and assumptions
- Length fields count UTF-16 code units; truncation, extra trailing text and invalid typed encodings are errors.
- JSON numeric scalars use JavaScript floating-point numbers. Supply a JSON string when an identifier’s exact large-integer digits must be preserved; strings and numbers remain distinct scalar types.
- String framing and alphabet digits use UTF-16 code units, not bytes or grapheme clusters. Exact integer text accepts a signed decimal spelling of at most 256 digits before operation-specific range checks.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Use typed framing when distinct scalar types or tuple boundaries must remain distinguishable. Keep alphabet, width, normalization and numeric bounds consistent between producers and consumers.
References
Similar or alternative tools
- Typed Scalar Key Decoder
Decode the explicit type-tagged scalar key dialect, validating canonical finite number spellings and exact UTF-16 string lengths.
- Typed Tuple Key Encoder
Encode a JSON scalar tuple as count plus length-prefixed typed scalar keys, avoiding concatenation ambiguity and preserving component types.