Ordered Object Key Selector
Select own object members in explicit order as entries, avoiding JavaScript integer-key reorder ambiguity; report absent names separately.
Description
Select own object members in explicit order as entries, avoiding JavaScript integer-key reorder ambiguity; report absent names separately.
An ordered key selection extracts object values in a caller-declared sequence. Returning entries as an array preserves that requested order explicitly.
When to use this tool
Select own object members in explicit order as entries, avoiding JavaScript integer-key reorder ambiguity; report absent names separately.
- Prepare the supplied objectJson, orderedKeys 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, orderedKeys. 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.entries, result.missingKeys. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require distinct nonblank orderedKeys. For each key in order, emit a key/value entry when present and otherwise append it to missingKeys.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 |
| orderedKeys | ordered 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.
[
{
"field": "objectJson",
"decoded": {
"b": 2,
"a": 1
}
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.entries | The entries list in the ordering and representation described above. |
| result.missingKeys | The missing keys list in the ordering and representation described above. |
{
"input": {
"objectJson": "{\"b\":2,\"a\":1}",
"orderedKeys": [
"a",
"x",
"b"
]
},
"output": {
"result": {
"entries": [
{
"key": "a",
"value": 1
},
{
"key": "b",
"value": 2
}
],
"missingKeys": [
"x"
]
}
}
}Limitations and assumptions
- Missing names are reported rather than filled. Keys are literal top-level names, and the array order does not depend on serializing an object's property order.
- 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
- Object Key Prefix Partitioner
Partition own JSON object members by exact literal key prefix; does not strip prefixes or interpret patterns.
- Object Key Rename Map
Simultaneously rename own JSON object keys from an explicit map; reject collisions with renamed or untouched keys.