Created
August 19, 2014 21:32
-
-
Save dg/00ae93962614dfcb7d41 to your computer and use it in GitHub Desktop.
DI: Symfony versus Nette
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
services: | |
newsletter_factory: NewsletterFactory | |
newsletter_manager: @newsletter_factory::get(@templating) | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
parameters: | |
newsletter_manager.class: NewsletterManager | |
newsletter_factory.class: NewsletterFactory | |
services: | |
newsletter_factory: | |
class: "%newsletter_factory.class%" | |
newsletter_manager: | |
class: "%newsletter_manager.class%" | |
factory_service: newsletter_factory | |
factory_method: get | |
arguments: | |
- "@templating" | |
you don't have to use parameters in Symfony, that is optional
That's actually a super-neat syntax. Any downsides? Should be possible to adopt this in Symfony, no? Are there already any efforts on the way?
Let's rectify symfony one:
services:
newsletter_factory:
class: NewsletterFactory
newsletter_manager:
class: NewsletterManager
factory: ['@newsletter_factory', get]
arguments:
- '@templating'
- you don't have to use parameters for your classes
- you're using a deprecated factory declaration
Random visitor passing by in 2019...
# symfony
services:
App\:
resource: '../'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See http://symfony.com/doc/current/components/dependency_injection/factories.html