Opened 17 years ago
Closed 17 years ago
#5484 closed (fixed)
render_to_string is undocumented
Reported by: | xian | Owned by: | James Bennett |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | render_to_string sprintsept14 | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | yes |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
django.template.loader.render_to_string is undocumented please document.
Attachments (2)
Change History (9)
comment:1 by , 17 years ago
Needs documentation: | set |
---|---|
Owner: | changed from | to
comment:2 by , 17 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 17 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
by , 17 years ago
comment:4 by , 17 years ago
Keywords: | sprintsept14 added |
---|
comment:5 by , 17 years ago
Earlier today I checked in a new document, docs/shortcuts.txt
, which documents render_to_response
. Can this patch be updated to refer to that new document to remove redundancy? Looks like we only have to document render_to_string
.
comment:6 by , 17 years ago
Patch needs improvement: | set |
---|---|
Triage Stage: | Ready for checkin → Accepted |
by , 17 years ago
Attachment: | 5484.2.diff added |
---|
Patch which links to new shortcuts documentation for render_to_response
comment:7 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Attached patch documents both
render_to_string
and
render_to_response
; because they're so similar (
render_to_response
is literally a two-line wrapper around
render_to_string
), they really should be documented in the same place.