Hey there- This is actually a big priority for us, and we've agreed that we'd like our error messages to go beyond just saying what happened to what the developer may have done wrong and how he/she can fix it. Of course, this couldn't really have been done well while development was very very active. So, to really track these down and make the exception messages sing, we need help from the community to report these situations and - ideally - send pull requests to fix them.
So, it's something we're working on - the more input we can get, the better these exception messages ultimately will be. For these specific situations, if you can find a better way to throw the exception or a better message, you should send in a pull request. If not, i'll put it on my list to try to re-create and look into. Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Tue, Mar 29, 2011 at 3:12 PM, badllama77 <[email protected]> wrote: > Before I get smooshed, this isn't a help request. I have been working with > the 2 version of the framework for a couple of weeks now. > The one problem I really have is incredibly vague error syndrome. An > example being when the profiler is active and there is a twig > template error, the profiler throws an exception. This would be fine if it > gave even the slightest hint of exactly where it is. Then > after clearing the cache the first run allows the twig exception to show, > but still requires too much to figure out where it is. > I got a twig parsing error that didn't even tell me what file was in error. > > There are other examples, this is just the most recent. It always seems to > come down to rolling through all of my config/controller/template > files to find the problem. Seems counter-intuitive to the purpose of the > exceptions. > > > -- > 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 > -- 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
