Start warning if fields or exclude are not defined on DjangoObjectType

[jkimbo]

So that model fields aren't accidentally exposed through DjangoObjectType I propose that we start warning if either fields or exclude aren't defined with the intention to error completely in the future. This would also align the API more with Django Rest Framework which hopefully makes it more familiar to most developers.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[radekwlsk]

@jkimbo is anyone working on it? If not I would be happy to help and prepare PR for this issue.

@dopeboy is assigned but for almost a year now.

[jkimbo]

@radekwlsk if you have the time that would be great! I don't think anyone is working on it at the moment.

[radekwlsk]

@radekwlsk if you have the time that would be great! I don't think anyone is working on it at the moment.

Great. I will start working on it tomorrow. You can assign me to the issue, @jkimbo .

[radekwlsk]

@jkimbo You can close this.

[jkimbo]

Thanks @radekwlsk