#36151: Non-editable FieldError raised when using a GenericForeignKey on a form.
-------------------------------------+-------------------------------------
Reporter: James Pic | Owner: James Pic
Type: Bug | Status: assigned
Component: | Version: 5.1
contrib.contenttypes |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by James Pic):
pushed test and docs, keeping the current behaviour and allowing to go
back to the previous one with explicit editable=True
we can also restore the previous behaviour with editable=True by default,
but I'm not convinced it was intended, given the hardcoding on
editable=False in the said commit
although, perhaps the author just reproduced what he saw: a class
attribute of editable=False
https://github.com/django/django/commit/6002df06713cb0a7050432263527a25754190c27
#diff-76b33afd71c30afb749a0de312cfe4a4578d78abae84a9d5db06388a4b1bc454L39
I'm willing to update the patch whenever a design decision is taken by
authority though
--
Ticket URL: <https://code.djangoproject.com/ticket/36151#comment:8>
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 visit
https://groups.google.com/d/msgid/django-updates/01070194ae689599-dfe4266d-c717-445e-91a7-b50be428e3be-000000%40eu-central-1.amazonses.com.
