Search and filter controls for Browsable API & Admin

[lovelydinosaur]

The search and filter classes should render in the browsable API in a way that ensures they can be used without having to manually edit the URL querystring.

[jpadilla]

👍 definitely very useful, but I'm wondering how exactly we'll make filtering work, since filtering can happen for different fields. Would it only work for SearchFilter?

[lovelydinosaur]

Ask me when I get there :p

More seriously tho: I've been assuming we'll need an interface on filter classes that can be used to define if and how they should render to HTML.

[carltongibson]

Any appetite for pushing whatever is needed/can be pushed into Django Filter here?

I'm more or less on top of the issues backlog there: next up is improving the documentation and then I wanted to think through where it's going — there's seems to be a tendency to sprout new Filter subclasses like mushrooms on a damp night — compatibility with DRF, whilst not everything, seems like an important feature

[lovelydinosaur]

@carltongibson I don't think we'll need to do much pushing into Django Filter. We can probably just add a simple wrapper around its own HTML generation stuff.

[carltongibson]

OK, well as needed.

[lovelydinosaur]

Not a distinction that we make any more: https://github.com/tomchristie/django-rest-framework/labels

[lovelydinosaur]

Still very much on the roadmap but I'd like to start tying up 3.1.0 since there's a bunch of great improvements in there already. We may have 3.2.0 for the first portion of HTML stuff and 3.3.0 for the final bit of the admin api work, but currently undecided (may just all be 3.2.0)