@eagleoutice/flowr - v2.13.14
    Preparing search index...

    The resolver's DerivedConstraint with its call site resolved to a readable location, so the evidence answers not only "it must be >= 4.2.0 because it calls filter(.by=)" but also where.

    interface GuessVersionEvidence {
        at?: NodeId;
        bound?: string;
        detail: string;
        function?: string;
        location?: string;
        origin: string;
        parameter?: string;
        partial?: boolean;
        source: ConstraintSource;
    }

    Hierarchy (View Summary)

    Index
    at?: NodeId

    the call site that carried the evidence, so a bound can point at the line forcing it

    bound?: string

    the version bound this constraint establishes, if any (e.g. >=1.1.0, <=2021-05-31)

    detail: string

    a human-readable explanation, e.g. dplyr::filter has parameter '.by' only from 1.1.0

    function?: string

    the qualified function that carried the evidence (for signature constraints)

    location?: string

    the location of the call that carried the evidence, e.g. 12:3 or helper.R:12:3

    origin: string

    the concrete origin of the constraint, e.g. project metadata, dplyr 1.1.0, dplyr::filter

    parameter?: string

    the argument/parameter that carried the evidence (for signature constraints)

    partial?: boolean

    Set when the bound only holds for some of the origin's own candidate versions (e.g. only the newer releases of dplyr require R >= 4.1). Such a constraint is reported but never filters, as picking another version of the origin avoids it.