News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Paul Jones:
Symfony Components Sometimes Decoupled, Sometimes Not
January 03, 2013 @ 11:09:26

In this new post to his site Paul Jones talks a bit more about coupling in frameworks (see some of his recent Aura posts for more), this time looking at how the Symfony framework defines "decoupled" based on its object structure.

Previously, on decoupling and dependencies, I said: "Some [Symfony] commenters were dissatsifed with my use of unit testing requirements to discover what a package really depends on, as opposed to what its composer.json file states." I'm willing to allow that the Symfony commenters here might be right. Let's try looking at Symfony's claims and see how they stack up.

Based on a list of components Symfony says don't have mandatory dependencies, he finds that - out of the fifteen given - four of them do have dependencies.

Does having mandatory dependencies make it a bad project? Not at all. It just means their statement of "no mandatory dependencies" (and related statements) is not true for all the components listed. Now, it may be that the Symfony folk have a different idea of what "decoupled" and "standalone" mean.
0 comments voice your opinion now!
symfony framework component decoupled standalone


blog comments powered by Disqus

Similar Posts

Paul Jones\' Blog: Solar 0.15.1 alpha released

Vid Luther's Blog: Talking to multiple databases with Symfony 1.2

Daniel Hofstetter's Blog: Use components from the Zend Framework with CakePHP

PHP-Tools Blog: Stubbles Blog is live!

Community News: Has Smarty's Time Come?


Community Events





Don't see your event here?
Let us know!


bugfix unittest podcast community zendserver series voicesoftheelephpant opinion laravel package library language introduction api framework install symfony release deployment interview

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework