File-Based Version Constraints

[roxblnfk]

Feature Request: File-Based Version Constraints

Description

Add support for reading version constraints from external files using a path notation in the extractPath property of the Download action configuration. This allows dynamically referencing version constraints from project files (like composer.json).

Use Case

When a project already defines version constraints in standard files (like composer.json), users should be able to reference those constraints without duplicating them in the DLoad configuration.

Implementation Details

Syntax

Allow the extractPath property to accept file paths in the format:

filename@path.to.property

Example:

composer.json@require.temporal/sdk

This would extract the version constraint from the require.temporal/sdk property in the composer.json file.

Behavior

1. When both version and extractPath (in file reference format) are specified, both constraints should be applied when matching versions.
2. The file path resolver should support multiple nesting levels with dot notation to traverse JSON/YAML structures.
3. Handle gracefully if the file doesn't exist or the property path doesn't resolve.

Example Configuration

<download 
  software="temporal" 
  extractPath="composer.json@require.temporal/sdk" 
/>