Miha, I am +1 with your latest proposal. It would allow quick checks without having to update the configuration.
Cheers, Victor On Wednesday, January 30, 2013 2:12:49 PM UTC+1, Miha Vrhovnik wrote: > > > On Wednesday, January 30, 2013 1:50:25 PM UTC+1, Lukas Kahwe Smith wrote: >> >> >> On Jan 30, 2013, at 13:47 , Miha Vrhovnik <[email protected]> wrote: >> >> > Hi *, >> > >> > am I the only one who finds the "There is no extension able to load the >> configuration for XYZ" annoying? >> > * the sf is preventing me to have a future proof config file >> > * you can't simply just comment out the bundles when trying to pinpoint >> which bundle is causing a problem without removing a bundle configurations >> > * sometimes one would like to run a command in dev enviroment with >> no-debug switch to prevent any logging which would cause the OOM errors >> > >> > What's others opinion on removal of this? >> >> we debated this topic a lot before we went stable. >> the inverse problem is that typos will be harder to figure out. >> >> regards, >> Lukas >> >> > I might have been to vague when I said let's get rid of it. > IMO this warrants a notice in a log either by php's error log aka > error_log function or via Logger interface. > > Regards, > M > -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security 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 --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
