#26648: related_query_name is not checked for correctness
--------------------------------------+------------------------------------
Reporter: koniiiik | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (System checks) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by charettes):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
> I'll open a WIP PR in a moment, but when I implemented this check, it
turned out that there's actually a test case already which treats
related_name='_' (without an explicit related_query_name) as valid. Is
that something we want to support?
No as it generates an unusable `related_query_name`.
--
Ticket URL: <https://code.djangoproject.com/ticket/26648#comment:2>
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/066.490bb90120c8d429a8fdd9fe42248a14%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
