Miroslav Shubernetskiy

do you have any specific issues you need help with? you should be able to subclass base backend and implement all abstract methods

That would require sorting which is currently not supported. Sorry.

https://github.com/miki725/django-url-filter/issues/10

http://127.0.0.1:8000/api/customers/?in_use__iexact=no will work

you can do: ```python class CustomerFilterSet(FilterSet): in_use = Filter(form_field=forms.CharField(), default_lookup='iexact') ```

relevant docs https://django-url-filter.readthedocs.io/en/latest/api/url_filter.filters.html#url_filter.filters.Filter

what do you mean api level?

that could be possible although its not that simple. `iexact` only makes sense for string fields. so the default will only have to apply where `iexact` is possible. but yes...

currently thats not possible out of the box. but you can do custom filters via callable filters - https://django-url-filter.readthedocs.io/en/latest/api/url_filter.filters.html#url_filter.filters.CallableFilter

That's expected. You can change the strictness mode on the filterset to raise errors vs default behavior of dropping the filter criteria.