I'm just thinking that consistency between the environments is important and, unlike Twig templates, it doesn't seem like hydrators/proxies are generated from code that will be changed very often (you occasionally modify an entity, then rebuilt hydrators/proxies).
On the check command, how could that help unless the check command is able to tell you that your proxies/hydrators are out-of-date and still need to be generated before pushing to production? Thanks for everyone's feedback. Ryan Weaver Lead Programmer - iostudio - Nashville, TN http://www.iostudio.com http://www.thatsquality.com Twitter: @weaverryan On Thu, Jan 20, 2011 at 7:22 AM, Lukas Kahwe Smith <[email protected]>wrote: > > On 20.01.2011, at 14:12, ryan weaver wrote: > > > Thanks for the good explanation guys. Two things then: > > > > - perhaps we should turn auto-generation off in all environments to be > consistent? > > well its set explicitly to the debug setting. so the setting is there right > there for everyone to see in config.yml > > > - it should be well-documented that the generation tasks be run after > every model change so that proxies/hydrators aren't an afterthought > > > > What do you guys think? If you don't generate hydrators, for example, the > error is simply a failed require call on a non-existent file in the cache > dir. It's not obvious what went wrong or how to fix it. That's really where > my concern lies. > > sure documentation is good, check command is better > > 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]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- 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
