Interpret command flag aliases in the parser
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Application-owned aliases implementation plan
|
||||
|
||||
Status: in progress; Stages 1–7 completed.
|
||||
Status: in progress; Stages 1–8 completed.
|
||||
|
||||
## Authority, baseline, and scope
|
||||
|
||||
@@ -465,6 +465,13 @@ canonical/alias clusters; `-cvq` consuming `vq`; `-qv=false`; explicit empty
|
||||
values for long, short, and aliased spellings; missing values; unknown cluster
|
||||
members; `--message --hlep` as a value; `--message=--hlep`; post-`--` operands.
|
||||
|
||||
**Completed:** The routed flag context now reaches the adapter through neutral
|
||||
flag-alias records. One adapter pass interprets canonical and alternate long
|
||||
and short spellings, preserves option values and terminator operands, and feeds
|
||||
only canonical flags to pflag. Raw values retain per-occurrence source
|
||||
spellings. Canonical short empty values now follow the same long-form boundary.
|
||||
Verified with root and both integration module suites using the local workspace.
|
||||
|
||||
## Stage 9: Wire execution and invocation identity
|
||||
|
||||
**Work**
|
||||
|
||||
Reference in New Issue
Block a user