No request passed to custom filter as self.request

Hi,

I could be doing something wrong or else this is a bug.

When creating a custom filter and I override the queryset as per the Filtering docs:

   @property
    def qs(self):
        # The query context can be found in self.request.
        print(self.request.user)
        return super(CustomFilter, self)

self.request is always None

[danpalmer]

Hey @syrusakbary any chance this could be released? It feels like a pretty major blocker (certainly is for our use case of filtering a list for a logged in user), and installing from master breaks a lot of Python packaging workflows, not to mention means that other unreleased and possibly untested code might be used in production.

[codekiln]

In my case, I was using DjangoFilterConnectionField, and I could see that it’s connection_resolver method wasn’t supplying the request parameter. If you look at the master branch, you can see that the request object was just added as a parameter in 1db1cbdd9. I don’t know why, but the latest version in PyPI is 2.0.0, which doesn’t include that commit. It seems as though we’re due for a release, but I can’t find any tickets saying when.