#34944: Missing or misinferred attributes in output fields of generated fields
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Owner: Om Dahale
Type: Bug | Status: assigned
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: field, database, | Triage Stage: Accepted
generated, output_field |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Sanders):
Thanks Simon. I think we all seem to be in consensus about explicit
output_field… Lily & I were chatting on Discord (Paolo I believe you're on
there too) about how it seems unavoidable. 👍
@Om Dahale Thanks, I was going to suggest actually starting with an easier
ticket as I assumed you were a new contributor? But if you feel like
you're up to the task then good luck, just be aware that someone else may
need to "take over" if things stall seeing as this is a release blocker ;)
--
Ticket URL: <https://code.djangoproject.com/ticket/34944#comment:16>
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/0107018bacc9bafe-7d92c5a5-18b9-4f8e-af63-f2228a51b490-000000%40eu-central-1.amazonses.com.
