Phpstan Symfony Laravel Package

Product Decisions This Supports

• Enhancing Developer Productivity: Integrate into CI/CD pipelines to catch type-related bugs early, reducing runtime errors in Symfony applications.
• Improving Code Quality: Adopt stricter static analysis for Symfony-specific components, aligning with best practices for maintainability and scalability.
• Build vs. Buy: Buy—this package is a low-cost, high-value solution for Symfony projects already using PHPStan, eliminating the need to build custom type-checking logic.
• Use Cases:
  • New Symfony Projects: Mandate its use during onboarding to enforce type safety from day one.
  • Legacy Codebases: Gradually introduce to reduce technical debt by surfacing hidden type inconsistencies.
  • CQRS/Message-Driven Architectures: Leverage HandleTrait support to ensure accurate return types in query buses (e.g., for domain-driven design).
  • Console Command Validation: Catch undefined arguments/options or invalid defaults before runtime.

When to Consider This Package

• Adopt if:
  • Your project uses Symfony 4.2+ and PHPStan for static analysis.
  • You prioritize type safety in dependency injection, controllers, forms, or console commands.
  • Your team follows CQRS or messenger patterns and needs precise return type inference for HandleTrait.
  • You’re maintaining a large codebase where runtime errors (e.g., undefined services, invalid parameters) are costly.
• Look elsewhere if:
  • You’re not using Symfony or PHPStan (this is Symfony-specific).
  • Your project is small-scale with minimal dependency injection complexity.
  • You lack developer buy-in for static analysis tooling (requires configuration and discipline).
  • You need runtime validation (use Symfony’s built-in validators or Behat instead).

How to Pitch It (Stakeholders)

For Executives:

"This package supercharges our Symfony codebase by automatically catching type-related bugs during development—saving hours in debugging and reducing production incidents. For example, it flags undefined services or invalid console command arguments before they reach QA. With minimal setup (a one-line Composer install), we get enterprise-grade type safety for free, aligning with our investment in PHPStan. The ROI? Fewer fire drills, faster onboarding for new devs, and code that’s easier to refactor."

For Engineers:

*"phpstan/phpstan-symfony turns PHPStan into a Symfony powerhouse. It resolves ambiguous return types in:

• Dependency Injection (e.g., ContainerInterface::get() now returns the exact service type).
• Controllers/Forms (e.g., FormInterface::getErrors() respects $deep/$flatten parameters).
• Messenger/CQRS (e.g., HandleTrait::handle() infers query bus return types).
• Console Commands (e.g., catches undefined arguments/options).

Setup: Add to composer.json, configure extension.neon with your container.xml, and run phpstan analyze. No runtime overhead—just pure static analysis. Pro tip: Pair with phpstan/extension-installer for zero-config installs."*

Key Selling Points:

• Zero false positives (unlike generic PHPStan, this is Symfony-aware).
• CI/CD-friendly (fails builds on type errors, enforcing quality gates).
• Future-proof (supports Symfony 5.3+ features like PHP config files).