#30149: Empty value selected check in Admin Filter prevents subclassing
-------------------------------------+-------------------------------------
Reporter: Sardorbek Imomaliev | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.admin | Version: 2.1
Severity: Normal | Resolution:
Keywords: admin | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hi Sardorbek,
As I commented on #28687, I'm not understanding your issue exactly:
> At first glance I can't see how both `bool(self.lookup_val_isnull)` and
`self.lookup_val_isnull` == 'False' evaluate as True in the Not Empty
case. (???)
I'm not seeing how this comes up:
> ...we will get both `Empty` and `Not Empty` choices rendered as selected
on `Not Empty`.
Can you provide a test case or sample project that shows exactly what you
mean here?
Sorry if I'm just being slow. I'll leave this open for a few days more to
await your reply. Otherwise I'll close as `needsinfo`.
--
Ticket URL: <https://code.djangoproject.com/ticket/30149#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/067.6e9d9e5182df9ec7e5fa9b11dae84e1a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
