@tikoci/centrs
    Preparing search index...

    Interface ExplainArgument

    One argument token, located in the text it was lexed from.

    The ordered list is the primary shape and the object view is derived from it (the phase-0 normal form: "an ordered token/argument list with spans, never a pre-reduced args object"). Order and multiplicity are observable here and are flattened by ArgumentReading.args, so a consumer that needs to know a name was given twice still can.

    interface ExplainArgument {
        kind: ExplainArgumentKind;
        name?: string;
        span: { end: number; start: number };
        text: string;
        value?: string;
        valueSpan?: { end: number; start: number };
    }
    Index

    Properties

    name?: string

    Attribute name / query word. Absent on a positional.

    span: { end: number; start: number }

    The whole token, in the coordinate space of the text passed to the lexer.

    text: string

    The token verbatim, for a positional and for rendering.

    value?: string

    The token's LITERAL value, quotes removed — for an attribute the part after =, for a positional the whole token.

    Absent means there is no literal value, whatever the kind: the source spells a substitution, an expression, or an escape this phase does not decode. A consumer rendering a runnable command must read this field, not text, and must treat absence as "not renderable" — text is the source bytes, which are not the value the device would receive. A query is always absent: ? words are a grammar of their own and splitting them is not this lexer's claim to make.

    valueSpan?: { end: number; start: number }

    Where the value sits, quotes INCLUDED. Absent whenever value is.