Miroslav Shubernetskiy

I like the idea and sound like it belongs here. I'll take a look when I can. Thanks On Tue, Jun 16, 2015, 7:07 AM JocelynDelalande [email protected] wrote: > Maybe...

Fix looks good. Waiting for the ci to pass. Check Travis logs for exact error.

dont think I have tested core api when viewset defines filterset. have you tried creating filterset explicitly?

hmm. usually worked for me. probably there is some edge case with some relations where it attempts to go in infinite loop.

not any simple way at the moment

when using Django ORM, form field to validate the value is generated by the model field itself - https://github.com/miki725/django-url-filter/blob/bea478fb85fabfffeeb59bfb449afb3700047534/url_filter/filtersets/django.py#L88 for date fields, that will usually be a `DateField` or `DateTimeField`...

@ohenrik sorry for the late response unfortunately currently thats not possible since different filtersets cant be mixed and matched. this is a great idea though. would be nice to be...

currently json fields are not supported. sorry.

no specific guidelines. the complexity with json fields is that it will require some structure changes to the library which im not sure how to proceed with yet. I have...

`CallableFilter` overwrites `lookups`: https://github.com/miki725/django-url-filter/blob/056828119fa35631ab8d8a9b481f305c3b6c64cc/url_filter/filters.py#L479-L496 sounds like a bug. dont remember if there was any reason for returning all lookups for `CallableFilter`