Package-Defined Custom Install Directories #42
Description
Allow packages to declare their own install target in metadata
The iBroStudio/composer-custom-directory-installer plugin lets each package itself define extra.custom-directory-installer.directory and optional suffix rules, shifting configuration into the package. This simplifies consuming projects by delegating path decisions to package authors.
Technical Issue & Solution:
Issue: Consumers must manually configure every third‑party package they wish to relocate.
Solution: Introduce support for a package‑sourced directive: if a dependency’s composer.json contains an extra.custom-directory-installer object with directory (and optional suffix/prefix rules), install that package to the indicated path by default, unless overridden in the root project’s config.
Scope & Goal:
- Read and validate extra.custom-directory-installer metadata for each dependency.
- Merge package‑level directives with project‑level installer-paths, giving precedence to explicit rules in the root config.
- Goal: Enable package maintainers to self‑document install paths, reducing consumer configuration overhead and alignment issues.