@eagleoutice/flowr - v2.10.2
    Preparing search index...
    interface AbsoluteFilePathConfig {
        absolutePathRegex: string | undefined;
        additionalPathFunctions: FunctionInfo[];
        include: { allStrings: boolean; constructed: boolean };
        useAsWd: string;
        [key: string]: unknown;
    }

    Hierarchy (View Summary)

    Indexable

    • [key: string]: unknown

    Hierarchy-Diagram

    UML class diagram of AbsoluteFilePathConfig
    Index

    Properties

    absolutePathRegex: string | undefined

    Extend the built-in absolute path recognition with additional regexes

    additionalPathFunctions: FunctionInfo[]

    The set of functions that should additionally be considered as using a file path. Entries in this array use the FunctionInfo format from the dependencies query.

    include: { allStrings: boolean; constructed: boolean }

    Include paths that are built by functions, e.g., file.path()

    Type Declaration

    • allStrings: boolean

      Include every string, even if it is not used as a file path, to count, strings must have a length of at least 3 chars

    • constructed: boolean

      Whether to include paths that are constructed by functions

    useAsWd: string

    Which path should be considered to be the origin for relative paths. This is only relevant with quickfixes. In the future we may be sensitive to setwd etc.