mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-30 17:16:10 +00:00
Code Issues 32 Releases Wiki Activity

[1.6.x] Fixed #22412 -- More nuanced advice re template filters and exceptions.

Browse Source 
Thanks Tim for review.

Backport of 7e3834adc9 from master
This commit is contained in:
Carl Meyer
2014-04-09 23:19:55 -06:00
committed by Tim Graham
parent e68c084ed1
commit 728fd27c00
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/howto/custom-template-tags.txt
View File

@@ -87,9 +87,11 @@ Custom filters are just Python functions that take one or two arguments:
For example, in the filter ``{{ var|foo:"bar" }}``, the filter ``foo`` would be For example, in the filter ``{{ var|foo:"bar" }}``, the filter ``foo`` would be
passed the variable ``var`` and the argument ``"bar"``. passed the variable ``var`` and the argument ``"bar"``.
Filter functions should always return something. They shouldn't raise Usually any exception raised from a template filter will be exposed as a server
exceptions. They should fail silently. In case of error, they should return error. Thus, filter functions should avoid raising exceptions if there is a
either the original input or an empty string -- whichever makes more sense. reasonable fallback value to return. In case of input that represents a clear
bug in a template, raising an exception may still be better than silent failure
which hides the bug.
Here's an example filter definition: Here's an example filter definition: