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

Zend Developer Zone: Zend Framework Team has a new Leader

Jamie Rumbelow's Blog: Named Scopes with CodeIgniter

Benjamin Eberlei: Symfony All The Things (Web)

Symfony Blog: Top 20 symfony plugins

Matthias Noback: Decoupling your (event) system


Community Events

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


community unittest wordpress voicesoftheelephpant laravel middleware introduction interview api language development series extension conference framework release library opinion podcast laravel5

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