Skip to content

Add advanced Dependency Manager/Checker supporting specific versions and instance access #12

@Zoriot

Description

@Zoriot

Feature Request:

Implement a Dependency Manager/Checker utility for Alps-Lib that:

  • Checks for required dependencies and validates their presence.
  • Allows specifying the required version(s) for each dependency (including version ranges or exact versions).
  • Provides direct access to the loaded dependency instances for use within the codebase.
  • (Optional) Provides a remote file of specifying version range for dependencies.

References:
For the logic we used before, look at the linked commits in #11.

Goals:

  • Improve reliability and maintainability by ensuring correct dependency versions are loaded.
  • Enable developers to programmatically access and interact with dependency instances after validation.

Why?
Current solutions do not support version-specific dependency checks, nor do they provide a standard way to access dependency instances after loading. This can lead to compatibility issues and duplicated logic across projects.

Scope:

  • Design a clear API for version specification (e.g., semver, exact, ranges).
  • Expose validated dependency instances via a standard interface or registry.

This should be widely usable across all BTE projects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions