Jonathan Kim

v3 branch updated to latest master

@patrys I just released v3.0.0b5 of graphene-django that should fix that issue. Can you try it and see?

@patrys thanks for the investigation. We should try and use `aiodataloader` and use async everywhere. The lack of async DB support in Django might be a blocker though. Could you...

Apologies @zeth , reopening the issue. If you have any time any help with the issue would be most appreciated.

@jarcoal I think you're right in your assumptions however the underlying ConnectionField class is defined in Graphene (https://github.com/graphql-python/graphene/blob/master/graphene/relay/connection.py) and the Relay GraphQL spec doesn't define the edges to be required:...

Thanks @tcleonard and @ulgens ! Please get in contact with @zbyte64 to organise. He has admin access on the repo so should be able to handle any problems. Here are...

@jakubste I'm not convinced that trying to build authentication into graphene-django is a good idea. The recommended way of dealing with authentication is to build it into your resolvers (ref:...

@jakubste sorry you're right we are talking about authorization not authentication. That was a typo. To restrict access at an object level using the `get_queryset` method that @zbyte64 implemented is...

@sbernier1 I think overriding the default resolver is the way to go and I like your example. I think creating something like an `AuthDjangoObjectType` could work. I'm thinking an API...

@sbernier1 why would you need to access the queryset? Conceptually the ObjectType doesn't have access to how it was resolved so I don't think it would be possible anyway. You...