Description
Canonicalize supplied option names through explicit aliases, retaining each chain and cycle evidence; no argv parsing or unknown option rejection.
An argv vector already consists of literal argument strings. Shell quoting and tokenization happen before this representation; joining argv elements with spaces does not reconstruct a safe command string. Option aliases, duplicates, arity and dependencies are application policies that these tools take explicitly.
Canonicalize supplied option names through explicit aliases, retaining each chain and cycle evidence; no argv parsing or unknown option rejection.
When to use this tool
Use this tool to canonicalize supplied option names through explicit aliases, retaining each chain and cycle evidence; no argv parsing or unknown option rejection.
How to use the tool and how it works
- Enter names, aliasesJson using the input definitions below. Serialize the JSON text fields in the decoded shape shown below.
- Run the operation. Resolve malformed-input errors before interpreting the result.
- Read result.names. Interpret signs, units, ordering and null values using the rules below.
Require distinct alias names, then follow exact name-to-target chains for each supplied option name. Return the visited path and terminal string, or terminal = null with cycle = true when traversal repeats a name.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| names | Caller-supplied option-name bank, interpreted as described for negation or aliases. | Dense list of at most 128 strings, each at most 8,192 UTF-16 code units. |
| aliasesJson | JSON array of {name,target} string aliases with distinct names; cycles are reported. | Text, at most 8,192 UTF-16 code units; the stated grammar and narrower limits also apply. |
These decoded examples show the structure of the JSON text fields. Supply each as its corresponding serialized JSON string.
{
"aliasesJson": [
{
"name": "v",
"target": "verbose"
}
]
}| Output field | Interpretation |
|---|---|
| result | Object containing the fields below. |
| result.names | Input-order alias resolution records with input, path, terminal and cycle. |
{
"input": {
"names": [
"v"
],
"aliasesJson": "[{\"name\":\"v\",\"target\":\"verbose\"}]"
},
"output": {
"result": {
"names": [
{
"input": "v",
"path": [
"v",
"verbose"
],
"terminal": "verbose",
"cycle": false
}
]
}
}
}Limitations and assumptions
- Unknown names without an alias remain their own terminal names; this is not an allowed-option or argv-syntax validator.
- Inputs are literal tokens or explicit records. The restricted long-name grammar is [A-Za-z0-9][A-Za-z0-9-]* where required. No universal option syntax, shell semantics or process execution is inferred.
- Every declared top-level input is required and unknown 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 within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.
Alternative or Complementary methods
Use the application’s option schema to choose arity, aliases and conflict policy. Pass a literal argv vector to the intended process interface; shell command construction requires separate quoting rules.
References
Similar or alternative tools
- Long Option Assignment Joiner
Format one literal long-option argv token under a restricted ASCII option-name grammar; returns one argument, not shell quoting.
- Long Option Assignment Splitter
Split one strict ASCII --long-name[=value] argv token at the first equals; no shell parsing or implicit next-token consumption.