Parameter Laravel Package

Product Decisions This Supports

• Dependency Injection (DI) Simplification: Enables cleaner, type-hinted parameter resolution in Laravel/PHP applications, reducing boilerplate for service binding and instantiation.
• Scalable Microservices: Ideal for modular architectures where services need dynamic instantiation with resolved dependencies (e.g., API clients, repositories, or third-party integrations).
• Roadmap for "Build vs. Buy": Justifies buying this lightweight package over custom DI logic, especially for teams prioritizing maintainability over reinventing wheel.
• Use Cases:
  • Resolving complex constructor parameters (e.g., new PaymentService($paymentGateway, $logger, $config)) without manual binding.
  • Dynamic service instantiation in plugins or SaaS multi-tenancy (e.g., tenant-specific services).
  • Reducing coupling in legacy codebases by leveraging PSR-11 containers (e.g., Laravel’s Illuminate\Container).

When to Consider This Package

• Adopt if:
  • Your team uses PSR-11 containers (e.g., Laravel’s container) and needs type-hinted parameter resolution without manual binding.
  • You’re building modular, dependency-heavy applications (e.g., APIs, CLI tools, or event-driven systems).
  • You prioritize developer velocity over micro-optimizations (package is ~200 LOC, minimal overhead).
• Look elsewhere if:
  • Your app uses non-PSR-11 containers (e.g., raw PHP arrays or custom DI).
  • You need advanced features like circular dependency detection (this package delegates to the container).
  • Your team lacks PHP 8+ (type hints are required).
  • You’re constrained by license compatibility (ISC is permissive but verify org policies).

How to Pitch It (Stakeholders)

For Executives: "This package lets our PHP/Laravel teams resolve dependencies automatically by type—cutting boilerplate and speeding up development. For example, instead of manually binding every service, we can instantiate new AnalyticsService() and let the container handle $client, $cache, and $config for us. Low risk (minimal code change), high reward (cleaner code, faster iteration)."

For Engineering: *"Problem: Manual service binding in Laravel is verbose and error-prone. Solution: respect/parameter resolves constructor parameters by type from the PSR-11 container (e.g., Laravel’s app()). Works seamlessly with existing DI and reduces coupling. Impact:

• Dev Experience: No more app()->bind() for every dependency.
• Maintainability: Aligns with modern PHP practices (type hints, PSR standards).
• Performance: Negligible overhead (~0 runtime cost). Next Steps: Spike integration in [Module X] to validate with our container setup. Target: Reduce DI boilerplate by 30% in new features."*