Hi Devs,
Any reason for not implementing the "AddBehaviors" option in by-table
basis, just like the isI18n attribute? Because I just want one or two
tables to support behavior, and don't want the other bunch filled with
unused code (you know, we've got enough generated by Propel ;). Just
change
if (DataModelBuilder::getBuildProperty('builderAddBehaviors'))
to
if (DataModelBuilder::getBuildProperty('builderAddBehaviors') || $this-
>getTable()->getAttribute('addBehavior'))
in SfObjectBuilder and SfPeerBuilder and things should work. So any
reason not to support this (I just start playing with mixins)? If not,
is this worth submitting a path?
Thanks in advance.
Tamcy
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
