Amnesia Laravel Package

Product Decisions This Supports

• Legacy System Modernization: Justifies a roadmap item to migrate from deprecated Symfony configurations (pre-5.3) to Laravel-native or Symfony 5.3+ alternatives, reducing technical debt and improving maintainability.
• Build vs. Buy Decision: Avoids reinventing configuration parsing logic by leveraging a pre-built solution (even if deprecated) as an interim step before adopting Symfony’s official ConfigBuilder or Laravel’s built-in tools.
• Use Cases:
  • Symfony <5.3 Migration: If the team is maintaining a Laravel app with Symfony components (e.g., bundles) that rely on legacy YAML/XML configs, this package could serve as a temporary bridge.
  • Dynamic Configuration Generation: For projects requiring runtime config overrides (e.g., CLI tools, packages) where Laravel’s static config/ files are insufficient.
  • Gradual Adoption of Symfony 5.3+: If the team is phasing in Symfony’s ConfigBuilder but needs to support older configurations in the meantime.

When to Consider This Package

• Only for Legacy Symfony <5.3 Systems: Use exclusively if actively maintaining a Laravel/PHP app that integrates with Symfony <5.3 and cannot immediately upgrade to Symfony 5.3+ or Laravel 8+.
• Look Elsewhere If:
  • Using Symfony 5.3+ or Laravel 8+: Replace with Symfony’s ConfigBuilder or Laravel’s native config() system.
  • Need Long-Term Support: This package is archived/deprecated; opt for maintained alternatives like:
    • symfony/yaml for YAML parsing.
    • spatie/laravel-config-array for Laravel-specific dynamic configuration.
    • Laravel’s built-in mergeConfigFrom for runtime overrides.
  • Active Community/Maintenance: Prioritize packages with recent commits, high stars (>100), and active issue resolution.
  • Non-Symfony/Laravel Projects: If the project is not using Symfony components, this package offers no value over native PHP or Laravel tools.

How to Pitch It (Stakeholders)

For Executives: "This deprecated package provides a short-term solution for parsing legacy Symfony configurations in our [X] system, but it’s a temporary workaround. We’re proposing a phased migration to Symfony 5.3’s native ConfigBuilder or Laravel’s built-in tools to eliminate technical debt and reduce long-term maintenance costs by ~25%. The risk is minimal—this is a one-time cleanup effort with no user-facing impact, and it aligns with our roadmap to modernize the stack."

For Engineering: "Symplify/Amnesia was a solid stopgap for Symfony <5.3, but it’s now obsolete. Here’s the plan:

1. Audit Usage: Run composer why symplify/amnesia to identify where it’s used.
2. Replace with Modern Alternatives:
   • For Symfony: Use ConfigBuilder (Symfony 5.3+).
   • For Laravel: Use spatie/laravel-config-array or Laravel’s mergeConfigFrom.
3. Scope the Effort: Focus on high-impact areas first (e.g., critical bundles or CLI tools). Pros: Eliminates deprecated code, future-proofs the system. Cons: Minimal effort if scoped correctly—this is a ‘no-brainer’ upgrade with zero trade-offs."

For Developers: "If you’re working with legacy Symfony configs (YAML/XML) in Laravel, this package can help transition to PHP-based configs. However, it’s deprecated, so we’ll replace it with:

• Symfony 5.3+: ConfigBuilder (native support).
• Laravel: spatie/laravel-config-array or service providers. No action needed yet—we’ll handle the migration in the next sprint. Let us know if you’re using this package so we can prioritize your area."