#27303: Allow FilterSpecs to return Q-likes
-------------------------------+--------------------------------------
Reporter: Yeago | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: 1.10
Severity: Normal | Resolution:
Keywords: filterspec | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by steve yeago):
I kept my patch intentionally simple and didn't try to solve any of those
other cases, but if there is some current wishlist or related tickets I
can consider them in a patch and move forward. But I think a greater
design decision should be made about this issue, though, because
regardless of the past I don't think that leaving the logical OR is
consistent or even intentionally used or realized by most implementors.
The filter().filter() issue is something that trips up even more
experienced Djangonauts.
--
Ticket URL: <https://code.djangoproject.com/ticket/27303#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 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/065.d263feed443594e4c5124fb813c86ede%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
