Propel Di Behavior Bundle Laravel Package

Product Decisions This Supports

• Dependency Injection (DI) for Propel Models: Enables clean, Symfony2-style DI for Propel ORM models, reducing manual service injection boilerplate and improving maintainability.
• Decoupling Business Logic: Facilitates separation of concerns by allowing Propel models to depend on Symfony services (e.g., logging, caching, external APIs) without tight coupling.
• Roadmap for Legacy Systems: Ideal for modernizing older Symfony/Propel applications where DI integration was previously cumbersome or nonexistent.
• Build vs. Buy: Avoids reinventing DI integration for Propel; leverages existing Symfony ecosystem (Symfony DI container) instead of custom solutions.
• Use Cases:
  • Injecting services like LoggerInterface, CacheInterface, or custom business logic into Propel models/queries.
  • Reducing repetitive Model::getService() calls or static service locators.
  • Enabling unit testing by replacing hardcoded dependencies with mocks/injectables.

When to Consider This Package

• Adopt When:
  • Your project uses Symfony2 + Propel ORM and lacks native DI support for models.
  • You need to inject Symfony services (e.g., Mailer, Cache) into Propel models/queries without manual wiring.
  • Your team prioritizes clean architecture and wants to avoid anti-patterns like static service locators.
  • You’re maintaining a legacy Propel codebase and want to incrementally adopt modern DI practices.
• Look Elsewhere If:
  • You’re using Symfony 3.4+ or 4/5/6, where Propel’s native DI support (via propel:model:build --di) may suffice.
  • Your project uses Doctrine ORM (this package is Propel-specific).
  • You require active maintenance (package has low stars/activity; evaluate risk).
  • Your team lacks familiarity with Symfony bundles or Propel behaviors.

How to Pitch It (Stakeholders)

For Executives: "This package lets us inject Symfony services (like logging or caching) directly into our Propel database models, reducing technical debt and making our codebase more maintainable. It’s a lightweight solution to modernize legacy systems without rewriting core logic. The MIT license and Symfony integration align with our existing stack, and it could cut development time for future features."

For Engineers: *"The c33s/propel-di-behavior-bundle bridges Propel’s ORM with Symfony’s DI container, so we can:

• Replace static service calls (e.g., Logger::log()) with injected dependencies.
• Test models in isolation by mocking injected services.
• Avoid boilerplate for service access in Propel models/queries. It’s a drop-in behavior for Propel models, requiring minimal setup. Tradeoff: Low community activity (evaluate for your risk tolerance)."*