Undefined default handling of non-strings in filters.

[hassanakbar4]

type_defect | by henrik@levkowetz.com

---

The resolution of ticket #182 raises the issue of what the default action of template filters should be: Pass through arguments that aren't of the expected type, or flatten and render them?

For instance, should parse_email_list() and make_one_per_line() in ietf_filters:

• Render None as "" ?
• Flatten lists ?
• Render non-string list elements, and other non-string args using str() ?

There are probably more cases of filters which now expects string input and will break if they are given None or other non-string.

---

Issue migrated from trac:184 at 2021-12-13 11:40:06 +0500

[hassanakbar4]

@henrik@levkowetz.com changed milestone from Soonish to Cleanup

[hassanakbar4]

@rjsparks@nostrum.com changed priority from major to minor

[hassanakbar4]

@rjsparks@nostrum.com edited the issue description

[hassanakbar4]

@rjsparks@nostrum.com changed status from new to archived