It would be soooooo cool to be able to count on a test-run with velocity to display us (in the face) all the exceptions velocity is silently swallowing!
Probably that's not entirely covered in this proposal, but something that diminishes my frustration of a velocity that keeps swallowing way too many exceptions. If we have a try/catch we can start making velocity less tolerant and, for example, stop the ridiculous conversion null == true == undefined == compilation-error that currently happens inside an #if. paul On 18 sept. 2014, at 19:23, Sergiu Dumitriu <[email protected]> wrote: > 1. I would rather add proper directives instead of macros and > uberspector hacks: http://stackoverflow.com/q/159292/620249 > > 2. So far it has been the job of our scriptable wrappers to catch > exceptions, does this proposal mean that: > a. We should stop doing that and write try-catch logic in our > templates/scripts? IOW, catching exceptions in wrappers is a bad design > pattern? > b. We didn't do that enough, and as a workaround we're adding exception > handling in Velocity? _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
