Tom Riat
Tom Riat
Hello @ozgurakcali, this bug should be fixed with my change in #66, try to get drf-tracking from the master branch and not from PIPY to see if it is solved....
Let me know if it worked better @ozgurakcali
Maybe @avelis can do a release as there is a bug in the actual version ?
Hello @palespring, it is pretty hard to know if it is a bug from DRF-tracking or not, I'd say it is not as I don't see it before and I...
I think it has been solved @avelis no? at least with my branch for Django2 we had travis running again edit: Ok I though it was something else, doing a...
Hello @ataylor32, actually all this things could be managed through the groups and not a params in the settings. Or maybe I don't understand correctly what you want, sorry
It is actually already a warning in 1.11 Let's do a PR for that :)
I did an other PR for compatibility but not related to Django 2.0 #93
I'll check tomorrow if I can do an other PR, thanks @tored11
@avelis it seems it requires a bit more things to do (adapt tests) because if you just change it, everything crash. I started a branch to work on and add...