Next: Deployment - Building standalone binaries, Previous: Templates, Up: Djula HTML templating system [Contents][Index]
Djula catches errors and barfs them to the template output by default.
That is controlled via the *CATCH-TEMPLATE-ERRORS-P*
variable.
If changed to NIL
, then errors are not caught anymore and are
debuggable from the lisp listener.
Djula provides more or less verbosity in template errors. Verbosity is
controlled via the variable *VERBOSE-ERRORS-P*
.
Also, there’s a fancy page to display errors, which can be disabled if
desired. That is controlled via the variable *FANCY-ERROR-TEMPLATE-P*
Use the debug
tag in your templates to display the arguments being passed to templates together with other debugging information.
Enable the *debug-mode*
for displaying debug information for all rendered templates.
When *strict-mode*
is enabled, access to variables not bound in templates signals an error.
For instance, trying to render {{foo}}
without passing a :foo
argument to render-template*
will signal an error. Whereas if strict mode is disabled, the variable access is bypassed and nothing is rendered.
Up: Errors and debugging [Contents][Index]
When enabled, caught errors during the rendering of the template are written to the output instead of being handled by the lisp listener. This is enabled by default.
When enabled, show a fancy template when an error ocurrs. This is enabled by default.
When enabled, errors are displayed more verbosely. Good for debugging. This is enabled by default.
When in debug mode, debugging information is attached to rendered templates.
When enabled, unbound template variables access signals an error.
Next: Deployment - Building standalone binaries, Previous: Templates, Up: Djula HTML templating system [Contents][Index]