Autowiring Bundle Autowiring Bundle

Easing the use of the Symfony dependency injection container.

So what's this all about? So what's this about?

Autowiring Bundle is an inofficial External link following.Symfony 2 bundle that provides the ability to define services by annotations (by php doc-comments that are interpreted as class metadata) and autowiring by naming convention and type resolution. These features are both enabled for pre-defined services as well as any container aware class (beeing more precisely: for any class).

Examples

A few LOC's can tell more than thousand words, so let's implement a WelcomeController for a freshly created Symfony 2 application.

  1. <?php
  2. namespace Acme\DemoBundle\Controller;
  3.  
  4. use Ifschleife\Bundle\AutowiringBundle\Annotations\Service;
  5. use Ifschleife\Bundle\AutowiringBundle\Annotations\Inject;
  6.  
  7. use Symfony\Component\Templating\EngineInterface;
  8.  
  9. /**
  10.  * @Service
  11.  */
  12. class WelcomeController
  13. {
  14.     /**
  15.      * @var EngineInterface
  16.      */
  17.     private $templating;
  18.  
  19.     /**
  20.      * @param EngineInterface $templating
  21.      * @Inject
  22.      */
  23.     public function __construct(EngineInterface $templating)
  24.     {
  25.        $this->templating = $templating;
  26.     }
  27.  
  28.     public function indexAction()
  29.     {
  30.         return $this->templatingService->renderResponse('AcmeDemoBundle:Welcome:index.html.twig');
  31.     }
  32. }

No abstract ActionController base class is needed at all, the dependencies (the templating) is resolved by introspecting the constructor´s argument types.

Another example, now wired by naming conventions:

  1. <?php
  2. namespace Acme\DemoBundle\Controller;
  3.  
  4. use Ifschleife\Bundle\AutowiringBundle\Annotations\Service;
  5.  
  6. /**
  7.  * @Service
  8.  */
  9. class WelcomeController
  10. {
  11.     /**
  12.      * @var Symfony\Bundle\TwigBundle\TwigEngine
  13.      */
  14.     private $templatingService;
  15.  
  16.     public function indexAction()
  17.     {
  18.         return $this->templatingService->renderResponse('AcmeDemoBundle:Welcome:index.html.twig');
  19.     }
  20. }

Or address the service explicitely to obviate dependency resolver conflicts:

  1. //...
  2. use Ifschleife\Bundle\AutowiringBundle\Annotations\Inject;
  3. /**
  4.  * @Service
  5.  */
  6. class WelcomeController
  7. {
  8.     /**
  9.      * @var Symfony\Bundle\TwigBundle\TwigEngine
  10.      * @Inject("templating")
  11.      */
  12.     public function __construct(EngineInterface $templating)
  13. //...
  14.  

There are many more means provided that enable you to steer the service resolving by enriching your classes with metadata information (annotation, variable namining conventions).

Additionally, the behaviour of the dependenceny resolver is highly configurable

For learning more, please refer to the Documentation page or read the README.rst file in the Resources/doc folder of the bundle.

Learn more about dependency injection

Warning

NOTE: This bundle is in a very early state of development. There is yet a lack of code coverage and no guarantee that it`ll work at any circumstances. Thus i want to make one advice:

Don´t ever use this bundle in production environments until this warning has disappeared!

For now, this bundle must be understood as a case-study for determining use-cases and solutions to them. It is an experiment to make out what may be achieved by dependency-autowiring, to determine which features are considered “good”, and ”bad“ in the sense of “too complex”, “too magically” or simply redundant.

So, if you are interested, read the docs, download the bundle and give it a try.

Thank you!