add exclude = () for DRF 3.3 compatability

[resalisbury]

"Serializers must include either a fields option, or an exclude option."
source: http://www.django-rest-framework.org/topics/3.5-announcement/#modelserializer-fields-and-exclude

alternate solutions proposed here: #26

[Brobin]

"Explicit is better than implicit". I like the fields version better, if we can figure out that it would be much better.

[resalisbury]

agree. it just happens to be more work :(. I'll play around with it a bit more...

[auvipy]

what about using 'all'

[Brobin]

@auvipy I don't belive all works with the versions of DRF that I'm supporting. I guess that could be up for discussion. Do I even need to support old versions of DRF?

[auvipy]

no you shouldn't

[resalisbury]

re: supporting older version. I wouldn't worry about it. drf-generators is for quickly creating a new api from scratch, not for generating code for a legacy application. If you're creating a new api, you should be using the latest version of things...

[Brobin]

Agreed. Okay, so let's try the all route. In this case could you also update the travis yml to not build the older versions of drf? That way it passes.

[Brobin]

Any update on this?

[resalisbury]

Busy with other things for now!