#20749: get_FOO_display does not return proper value or warn for inconsistent
type
-------------------------------------+-------------------------------------
Reporter: ellisd23@… | Owner: ellisd23
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by ellisd23):
Yeah, I figured this was at least a step in the right direction. Is there
a way we could generically test that the type of the choice aligns with
the chosen field? I'll dig around in the code for the fields.
I'm worried that with option 2, since these methods would likely be used
frequently in templates, it would lead to a large number of warnings. It
seems like option 1 would be more "pure" as well, since your types really
should match the field as it will be stored and returned.
--
Ticket URL: <https://code.djangoproject.com/ticket/20749#comment:7>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/076.6f7ff77048cde1cac7b90ed1ac153eb2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
