Opened 7 years ago
Last modified 7 years ago
#28190 closed Cleanup/optimization
Clarify absolute/relative paths in the extends/include template tag docs — at Version 1
| Reported by: | Anupam | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.11 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Minor point but I feel it is worth re-iterating that the example (https://docs.djangoproject.com/en/1.11/ref/templates/builtins/#include) is using an absolute path and folks should prefix "./" if the template being referenced is in the same directory as the template that is referencing it.
Change History (1)
comment:1 by , 7 years ago
| Component: | Uncategorized → Documentation |
|---|---|
| Description: | modified (diff) |
| Has patch: | set |
| Patch needs improvement: | set |
| Summary: | Re-iterate the point about absolute/relative paths in the 'include' templatetag example → Clarify absolute/relative paths in the extends/include template tag docs |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Uncategorized → Cleanup/optimization |
Note:
See TracTickets
for help on using tickets.
As I said on the PR, I'm not sure if "absolute path" is good terminology to use, considering that the given path is usually relative to the directory specified by a template loader, however, some clarifications could be made.