First, I want to thank you all for taking the time to comment the first
RFC. After the discussions that took place, I have created a version 2
of the RFC:
http://symfony-reloaded.org/rfc/controllers
It hopefully takes into account all the feedback we had. Some personal
feelings after writing this second version of the RFC:
* Testability is not a valid concern: As the container implements the
ArrayAccess interface (to access parameters) and the `__get` and `__set`
methods (to access the services), creating one for testing is super-easy.
* Lots of people agree that passing dependencies as arguments
(constructor or action methods) is the way to go but these approaches
involve some magic.
* There is no "best approach". Each has some pros and cons. We need
to find the approach that fits best Symfony 2 philosophy.
Some approaches have not been included in the RFC for the following reasons:
* Approaches that need code generation;
* Approaches that does not feel like PHP code;
* Approaches that involves too much overhead.
Based on the naming convention of the Dependency Injector issue raised
by Jordi, I will write another RFC on that topic.
Now, let's resume the discussion on this new version of the RFC!
Fabien
--
Fabien Potencier
Sensio CEO - symfony lead developer
sensiolabs.com | symfony-project.org | fabien.potencier.org
Tél: +33 1 40 99 80 80
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
To unsubscribe from this group, send email to symfony-devs+unsubscribegooglegroups.com or
reply to this email with the words "REMOVE ME" as the subject.
