MultipleChoiceFilter does not use lookup_type

[lexotron]

MultipleChoiceFilter.filter() should be updated to include something along these lines:

def filter(self, qs, value):
    (...)
    lookup = self.lookup_type or 'exact'
    for v in value:
        q |= Q(**{'%s__%s' % (self.name, self.lookup_type): v})
    (...)

I haven't really taken a good look at any of the code, so this is just my initial solution.

[nkryptic]

This is very true and could easily be addressed by the above code. But, should a MultipleChoiceFilter ever perform a non-exact query? Is there a use case for that?

[nkryptic]

Forget the question... I can see possible use cases, although there might be alternatives. Maybe something where the choices are used with an iexect, icontains or iregex? Either way, looks like this should be addressed at some point.

[carltongibson]

I'm going to close this as Out of Scope for the moment. Happy to consider documented, tested pull requests. We may have capacity to reconsider in the future.

[rixx]

Is your offer still open? Adding lookup_expr to MultipleChoiceFilter should be a very short PR (think one or two lines, plus tests), and might be useful to more people. I just added it to my project by overriding get_filter_predicate as the class docs suggest, but it took me a while to figure out that I should do this.

[carltongibson]

Hey @rixx! Yep. Very happy to look at a PR here. (Thanks! 🤹‍♂️)