#34531: Rendering form throws deprecation warning
-------------------------------+--------------------------------------
Reporter: Petr Dlouhý | Owner: nobody
Type: Uncategorized | Status: closed
Component: Forms | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Petr Dlouhý):
Replying to [comment:3 Mariusz Felisiak]:
> I'm not sure how it could be clearer.
I see few options:
* Change link in the deprecation message from
https://docs.djangoproject.com/en/4.2/releases/4.1/ to
https://docs.djangoproject.com/en/4.2/releases/4.1/#forms to point users
to the right section.
* There is no explicit note that casting form to string will raise
deperecation warning. I would add an explicit bullet regarding `{{ form
}}` tags especially for developers of third party applications (where
setting `FORM_RENDERER` might not be viable option) saying something like:
Directly casting forms to string, e.g. with `{{ forms }}` will throw a
deprecation warning now. It can be resolved either by setting
`FORM_RENDERER` or by explicitly using one of `form.as_div()`,
`form.as_ul()`, `form.as_table()`, `form.as_p()`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34531#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/01070187e1e6f9b4-719906b6-af25-48e7-a922-5b468f456d90-000000%40eu-central-1.amazonses.com.
