This has also been one of my main painpoints with NV. The parser will not report anything if you misspell a variable and you really have to bee on the lookout after refactorings to avoid some $foo texts appearing on your website. There should be some way to turn the NV parser into verbose mode where it will generate Log4Net warnings whenever it can't match a variable etc. The default behavior of going to String.Empty if $foo is not provided in the context is quite problematic during development.
greetings Daniel On Sat, Sep 12, 2009 at 2:46 AM, JakeS <[email protected]> wrote: > > I'd love to hear if there is one, but my suspicion is there isn't. > You just have to look at the context being passed to the template and > ensure it matches. The parser will provide some rudimentaty syntax > error exceptions. > > On Sep 10, 7:41 am, jamesfarrer <[email protected]> wrote: > > Hi, > > > > When working on my monorail project, if I have an error in my > > nvelocity view, it just returns a blank screen. I have to manually > > look through the view for the problem. > > > > Is there any way to turn on some kind of logging / debug so I can see > > where the problem is? > > > > Thanks > > James > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
