Choices frontend

[erfaan]

Fixes #175

[bufke]

Thanks for contributing! Is this a work in progress?

ng-if="!field.choices" needs to be ng-if="!field.field_choices"

Once that is fixed though I get:

Another consideration to make is that some filter types don't make sense with a single select box. For example I may want to filter with the In type where I'd expect to enter multiple values.

[erfaan]

The simplest way to enable choices in FilterFieldSerializer seems to be to add choices field which is already available in model FilterField. It can work for both new filters and saved filters if we change field_choices to choices as well.

Regarding, rendered output, I was using Choices from django-model-utils to create choices and it worked for that. May be we need to modify the get_choices method and return the neutralized choices.

Yes, I agree, we should render textbox for some filter types (in).

[erfaan]

I have made the name of choices key consistent across different APIs and added support for choices of type Choice from django-model-utils