#35772: Document models.Field.contribute_to_class
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
Type: | Gama
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: contribute_to_class | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Clifford Gama):
> I half-agree with this. I do think that it's weird to mention something
in the public docs that is not public, but at the same time, providing
that pointer could be very useful for some very specific cases.
I agree. However, I’m not sure that the current approach is the best way
to handle it. When something is mentioned in the documentation, you expect
that either it's explained there or at least linked to further details.
That said, I don’t have an immediate solution either.
> My proposal to go to the forum can instead be repurposed to ask for
feedback about removing the reference, or leaving it as is, un-referenced?
Yes, I'll open up a discussion on this, but I’ll hold off until after I’ve
put together a draft PR for #27880, which is tied up with
`contribute_to_class`.
--
Ticket URL: <https://code.djangoproject.com/ticket/35772#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701920b6cfac0-b5308593-0f0e-4072-885b-9d64006dbc2f-000000%40eu-central-1.amazonses.com.
