#949 closed defect (wontfix)
[patch] include template tag should support select_template type list
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Template system | Version: | dev |
| Severity: | normal | Keywords: | |
| Cc: | upadhyay@… | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
<% include template_name %> includes the named template which is like get_template of the Python API for loading templates, for consistancy we should have a comma seperated template list similer to select_template. (Untested) Patch attached.
Attachments (1)
Change History (5)
by , 19 years ago
| Attachment: | django.patch added |
|---|
comment:2 by , 19 years ago
| Cc: | added |
|---|---|
| Component: | Admin interface → Template system |
| Summary: | include template tag should support select_template type list → [patch] include template tag should support select_template type list |
| Version: | → SVN |
Now that I think about comma vs spaces, the best option may be pipe character "|" as it already implies logic "or" which conveys what is happening.
comment:3 by , 19 years ago
The point is that we shouldn't be proliferating random syntax within template tags.
The current method of parsing within a tag does little to discourage this, but people should explicitly *not* have to go and look up what random syntax someone made up for a particular tag.
comment:4 by , 19 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
This is out of the scope of the built-in {% include %}. Use a simple custom tag if you need this behavior.
takes a comma seperated list as include argument