#33437: Add possibility to render fields individually using as_p, a_table and
as_ul
----------------------------------+--------------------------------------
Reporter: Christophe Henry | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 4.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Hi Christophe. Thanks for the proposal.
I think this would be too much API, for little benefit. As David says,
leaning towards the new template based form rendering is the way to go,
and we're looking at deprecating the various `as_p()` &co methods.
If you wanted this kind of this, and the inbuilt rendering isn't enough
for you, I'd look towards third-party packages (such as Crispy Forms,
Floppy Forms, Django Sniplates, ...and so on) , or adding a custom tag
taking a form field to your own project. (I hope one of those options
helps :)
Thanks again.
--
Ticket URL: <https://code.djangoproject.com/ticket/33437#comment:4>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.7e9b96499a5086ca5faee99b82e60c55%40djangoproject.com.
