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

    The options every slicing query understands, independent of how it picks the nodes to keep.

    interface SliceQueryOptions {
        includeCallees?: boolean;
        inlineFull?: InlineFull;
        inlineSources?: boolean;
        noMagicComments?: boolean;
        noReconstruction?: boolean;
    }

    Hierarchy (View Summary)

    Hierarchy-Diagram

    UML class diagram of SliceQueryOptions
    Index

    Properties

    includeCallees?: boolean

    If set (and slicing backward), continue the slice past a function-definition boundary, also including the definition's binding and call sites. Defaults to false.

    inlineFull?: InlineFull

    Inline every file into the reconstruction, in flowR's loading order (which respects implicit sources), independent of whether it is sourced explicitly; 'banner' additionally precedes each file with a banner comment naming it. Overrides inlineSources.

    inlineSources?: boolean

    Inline resolvable source() calls into the reconstruction so the result is a single self-contained R text. Cyclic and unresolvable source() calls are kept verbatim and reported via reconstruct.inlineWarnings.

    noMagicComments?: boolean

    Should the magic comments (force-including lines within the slice) be ignored?

    noReconstruction?: boolean

    do not reconstruct the slice into readable code