Opened 4 years ago
Closed 4 years ago
#31673 closed New feature (wontfix)
Equivalent to {{ form }} for generic detail view
| Reported by: | Jon Renshaw | Owned by: | nobody |
|---|---|---|---|
| Component: | Generic views | Version: | 3.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
It would be useful if there was an equivalent to the form template function including as_p, as_table and as_ul for the generic detail view. At the moment you have to manually enter into your template the fields you want to display for views sub classed from generic.DetailView whereas in the generic create and update views these can be entered as a list named fields in the view definition and then you can simply include {{ form }} in your template.
Note:
See TracTickets
for help on using tickets.
I think this would need some consensus on the DevelopersMailingList. I'm not immediately convinced that such a generic function would be applicable to a large number of use cases. If you implement something for your project, feel free to open a discussion with a more specific proposal on the mailing list.