#30577: Custom rendering for readonly fields in admin
-------------------------------+------------------------------------
Reporter: David | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Federico Capoano):
Thank you Sarah for accepting the ticket. Now the question is whether we
want to simply continue supporting the workaround or whether we want to
provide an official cleaner way to implement this, although probably
having both available initially could provide a backward compatibile
upgrade path (eg: previous implementations will continue working, we can
advise to migrate to the new way in the release notes and warn that the
previous workaround is deprecated and will be removed in the next
release).
--
Ticket URL: <https://code.djangoproject.com/ticket/30577#comment:15>
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 visit
https://groups.google.com/d/msgid/django-updates/010701983ca73dee-7a6f418b-10cc-4cbb-a306-68a3664f5adf-000000%40eu-central-1.amazonses.com.
