On 3/28/11 4:17 PM, Lukas Kahwe Smith wrote:
On 28.03.2011, at 15:55, Fabien Potencier wrote:
I have already said my point of view: the components should be as decoupled as
possible as so we need to keep the keys as they are now.
I understand why keys are better for *end* user projects, but this is not the
case for the core framework. As is, Validator and Translation components are
decoupled. If we were to use keys, that won't be the case anymore.
well we could bundle a super simple "translation" implementation for these components that just works
with hardcoded array maps key => value. this way people that do not use Symfony2 still get
"decent" error/validation messages out of the box, but Symfony2 core doesnt "suffer". this
would not really diminish the out of the box experience for standalone component users and provide an extension
point for Symfony2 to hook in the translation system.
I don't see how this could work. In the validation component, you will
need to implement some kind of interface for your translation
implementation, but for sure not the interface from the Translation
component. How do you integrate the translation component then?
Fabien
regards,
Lukas Kahwe Smith
[email protected]
--
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
