@adcp/sdk API Reference - v7.9.0
    Preparing search index...

    Interface BindingMatch

    interface BindingMatch {
        binding: CatalogBinding;
        raw_value: string;
        expected_encoded: string;
        observed_url: URL;
        record: TrackerUrlRecord;
        position:
            | { kind: "query"; key: string; index: number }
            | { kind: "path"; index: number }
            | { kind: "href_whole_value" };
        observed_value: string;
        is_custom_vector: boolean;
    }
    Index

    Properties

    The binding this match satisfies.

    raw_value: string

    The raw_value resolved from the fixture vector (or the inline override).

    expected_encoded: string

    The expected_encoded resolved from the fixture (or the inline override).

    observed_url: URL

    Parsed observed URL whose aligned position produced observed_value.

    The tracker record this observation came from (attribute, tag, line hint).

    position:
        | { kind: "query"; key: string; index: number }
        | { kind: "path"; index: number }
        | { kind: "href_whole_value" }

    Alignment position inside the template. href_whole_value indicates the macro occupied the entire attribute value — subject to assert_scheme_preserved.

    observed_value: string

    Observed value at the aligned position — the bytes emitted after substitution.

    is_custom_vector: boolean

    True when the binding was resolved via inline raw_value / expected_encoded overrides rather than a canonical fixture vector. The contract's error_report_payload_policy requires custom vectors to be SHA-256 redacted in error reports — the assertion helpers honor this flag when populating AssertionResult.observed and .expected.