#31026: Switch form rendering to template engine
--------------------------------------+------------------------------------
Reporter: Johannes Hoppe | Owner: nobody
Type: Cleanup/optimization | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
I think that it makes sense. It'd be great if you could do a bit of
research on #15667 to figure if this was simply overlooked or if there was
a reason for not doing it in the first place.
I think there's also a ticket out there to allow `Form.__str__()` to use
`as_p` or `as_ul` instead of `as_table` by default. If we were using
template based rendering we could simply define a
`django/forms/default.html` that `{% include "django/forms/table.html"
%}`, use it in `.__str__()` and document that the former must be
overridden to achieve the desired behaviour.
--
Ticket URL: <https://code.djangoproject.com/ticket/31026#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.8bce6b5d57cb99d2c301c2a451d22bf1%40djangoproject.com.
