#32848: Bad error with invalid lookup on annotated field.
--------------------------------+--------------------------------------
Reporter: Gordon Wrigley | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
Hi Gordon. Thanks.
Hmmm. "Cannot resolve keyword 'bob' into field." is exactly what I'm
expecting here. 🤔
I'm going to say `needsinfo`: If you want to suggest a patch implementing
the logic for a better error message here then happy to look at it — but
I'm initially sceptical that backing out of the lookup resolution in order
to check if an annotation was applied is going to be worth the complexity.
However, if something clean is available then it's worth considering.
I hope that makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/32848#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.1693ea490e6345777419c7b1288d7e57%40djangoproject.com.
