Get queryset

[zbyte64]

My attempt at adding support for DjangoObjectType.get_queryset as described as Option 1 for #79 ; Tried to match up the method call as much as possible but dropped request and args as I wanted get_node to also be able to call get_queryset .

[coveralls]

Coverage increased (+0.03%) to 94.547% when pulling ad2688f on zbyte64:get_queryset into f76f38e on graphql-python:master.

[zbyte64]

After reviewing graphql-python/graphene#846 I think this would be better served by a permission class. In the future a DjangoConnectionField could consult it's permissions for more specific permission actions like filtering objects on a connection.

[maarcingebala]

This is something that I wanted to implement in my project and then I found this PR. There is a lot of cases when I'd like to be able to limit the queryset used underneath when resolving nodes so I think it's a must-have for graphene-django.

I took a look at the permissions PR you linked above and I think the solution you proposed is fine for now. Overriding a function that returns the queryset is a common pattern used in class-based views or DRF; it's also simple to use and explicit.

[jkimbo]

This seems like a good idea!