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

    Manages the project's dependencies, their versions, and their interplay with FlowrAnalyzerPackageVersionsPlugins.

    Hierarchy (View Summary)

    Implements

    Hierarchy-Diagram

    UML class diagram of FlowrAnalyzerDependenciesContext
    Index

    Constructors

    Properties

    The linked full project context, allowing plugins to modify and access it.

    The functions context associated with this dependencies-context.

    name: "flowr-analyzer-dependencies-context" = 'flowr-analyzer-dependencies-context'

    A human-readable name of the context. Try to make it unique to avoid confusion in the logs.

    The plugins registered for this context. These build the foundation for applyPlugins.

    Methods

    • Register a dependency declared by a project metadata file (DESCRIPTION, renv.lock, rv.lock). Gated by solver.sigdb.loadProjectDependencies: when project-dependency loading is disabled this is a no-op, so the declared deps never enter the context (unlike addDependency, used for on-demand signature-database resolution).

      Parameters

      Returns this

    • Get the dependency with the given name, if it exists.

      If the static dependencies have not yet been loaded, this may trigger a resolution step. Pass version to pin the resolution to a constraint (an exact version string, or a Range; uncached; versionOverrides config still wins, base-R stays tied to the assumed R version); otherwise the version comes from the declared constraints.

      Parameters

      • name: string

        The name of the dependency to get.

      • Optionalversion: string | Range

        Optional version constraint to pin the resolution to (exact version string or a Range).

      Returns Package | undefined

      The dependency with the given name, or undefined if it does not exist.

    • The versions a dependency can possibly have, combining everything declared for it (a DESCRIPTION range, an rproject.toml entry, a lockfile pin, ...). undefined if the dependency is unknown, if nothing constrains it, or if the sources contradict each other -- then no version is possible at all.

      For why it is what it is (the individual constraints, or the version the database resolved to), take the Package from getDependency.

      Parameters

      • name: string

        The name of the dependency.

      Returns Range | undefined