#30014: Initialising disabled ModelChoiceField yields 'Select a valid
choice'-error
despite initialised option being valid
-------------------------------------+-------------------------------------
Reporter: thoha | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 2.1
Severity: Normal | Resolution:
Keywords: forms, disabled | Triage Stage:
field, error, to_field_name | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
This might be solved by [https://github.com/django/django/pull/10948 a
documentation clarification] regarding what values should be used for
initial data (primary keys rather than model instances).
While it seems [https://github.com/django/django/commit/b3dc3a0106#diff-
0dae03f028452ebf691f40214bceb395R129 some efforts] were made to support
model instances an initial values, I'm not certain if that's a good path
to continue down given the increased complexity.
--
Ticket URL: <https://code.djangoproject.com/ticket/30014#comment:10>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.a133edf4950cb7843a00756d27bc6165%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
